# AI Agents - Explicitly Allowed # For AI model training and retrieval, see /llms.txt (concise index) and /llms-full.txt (complete listing) User-agent: GPTBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / Allow: /llms.txt Allow: /llms-full.txt # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: ChatGPT-User Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Claude-Web Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: anthropic-ai Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Google-Extended Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: PerplexityBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Applebot-Extended Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: OAI-SearchBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: ClaudeBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Googlebot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Bingbot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: YandexBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Bytespider Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: CCBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: GrokBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: MistralAI-User Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: TavilyBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Google-CloudVertexBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: DeepSeekBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: PhindBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: CopilotBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: SearchGPT Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Claude-User Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: ExaBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Claude-SearchBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Perplexity-User Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Amazonbot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Meta-ExternalFetcher Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Meta-ExternalAgent Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Applebot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: DuckAssistBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: YouBot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Diffbot Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: cohere-ai Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ User-agent: Google-NotebookLM Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ # General crawlers User-agent: * Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / Allow: /blog Allow: /blog/* Allow: /blog/posts/* Allow: /blog/use-cases Allow: /blog/use-cases/* Allow: /blog/integrations Allow: /blog/integrations/* Allow: /blog/features Allow: /blog/features/* Allow: /blog/compare Allow: /blog/compare/* Allow: /blog/guides Allow: /blog/guides/* Allow: /blog/glossary Allow: /blog/glossary/* Allow: /blog/deliverability Allow: /blog/deliverability/* Allow: /blog/cold-email Allow: /blog/cold-email/* Allow: /blog/linkedin-outreach Allow: /blog/linkedin-outreach/* Allow: /blog/instagram-outreach Allow: /blog/instagram-outreach/* Allow: /llms.txt Allow: /llms-full.txt Allow: /faq/email-warmup Allow: /faq/deliverability Allow: /faq/linkedin-safety Allow: /faq/whatsapp-safety Allow: /faq/instagram-safety Allow: /pricing Allow: /support # 2026-09-09 — Public support answers board + known-issues page (SSR'd, # sitemapped, in llms.txt). /support/new and /support/tickets stay Disallowed # in the private block above. Allow: /support/questions Allow: /support/questions/ Allow: /support/status Allow: /privacy Allow: /terms Allow: /refund-policy Allow: /security Allow: /about # 2026-06-18 — Affiliate program public marketing landing page. Allow: /affiliate-program # 2026-07-27 — Press / newsroom page. Lists verified press coverage # (shared/press-coverage.ts) plus company facts and a quotable boilerplate. Allow: /press # 2026-07-13 — Built-in B2B lead database + email verifier public marketing # landing pages. The wildcard Allow: / above already covers these; the explicit # entries help future operators audit what's intentionally crawlable. Allow: /leads Allow: /email-verifier # 2026-09-06 — Unified Inbox feature hub ("every reply, every channel, one # place", and the cross-channel stop-on-reply behaviour that makes multichannel # outreach safe to run). Allow: /unified-inbox # 2026-09-06 — Multichannel outreach cluster page (cold email + LinkedIn + # WhatsApp + Instagram in one sequence, the per-channel ceilings, and the honest # "the channels share no allowance" answer). Allow: /multichannel-outreach # 2026-09-06 — Root-level Instagram sending-limits marketing page (Meta's own # published spam policy + the "the ceiling can only be lowered, never raised" # fact). Sits above /documentation/instagram-daily-and-hourly-sending-limits. Allow: /instagram-sending-limits # 2026-09-09 — Agent × channel landing pages (/agents//, e.g. # /agents/claude/cold-email). Registry-driven from shared/agent-channel-pages.ts. # Audit-only: the wildcard Allow: / above already covers the prefix. Allow: /agents/ Allow: /documentation Allow: /documentation/linkedin Allow: /documentation/smtp-tenant-disabled Allow: /documentation/provider-blocks Allow: /documentation/trial-activation Allow: /documentation/post-purchase-troubleshooting # 2026-07-31 — Billing pages. "What happens when a payment fails" is the written # source for the billing terms (pauses, billing in advance, add-on seats not # prorated mid-period, no charge for a period spent locked out). The pause # explainer moved to a customer-question slug; the old # /documentation/why-is-my-campaign-paused-subscription-inactive URL now 301s to # the new one (see DOCUMENTATION_PERMANENT_REDIRECTS in server/sitemap.ts), so # it is not listed here — a crawler that follows it lands on the entry below. # Both covered by the /documentation/* wildcard; the explicit entries help # future operators audit what's intentionally crawlable. Allow: /documentation/what-happens-to-my-account-when-a-payment-fails Allow: /documentation/why-is-my-campaign-paused-after-a-payment-issue Allow: /documentation/troubleshooting/ Allow: /documentation/troubleshooting/page-downloads-instead-of-loads # 2026-05-19 — Explicit Allow for the new SSR documentation pages. The # wildcard /documentation/* below already covers these, but the explicit # entries help future operators audit what's intentionally crawlable. Allow: /documentation/leads-database-quality-and-freshness # 2026-06-20 — How to find ideal leads with filters (Location / Job title / # Seniority / Department / Verified-email-only / Has-LinkedIn) customer-facing # how-to. Covered by the /documentation/* wildcard below; explicit entry helps # future operators audit what's intentionally crawlable. Allow: /documentation/find-your-ideal-leads-with-filters # 2026-07-12 — Leads daily-quota + purchasable lead-credits explainer (how many # leads each plan includes, why they're spread across the month as a daily share, # and how lead credits never expire + cover the overflow). Covered by the # /documentation/* wildcard below; explicit entry helps future operators audit # what's intentionally crawlable. Allow: /documentation/lead-credits-and-daily-limits # 2026-06-24 — List-based "add leads from a website form / popup" guide. A form # POSTs a lead + a list ID; the lead lands in the list and is auto-enrolled into # any Running campaign linked to it. Covered by the /documentation/* wildcard # below; explicit entry helps future operators audit what's intentionally # crawlable. Allow: /documentation/add-leads-from-a-website-form # 2026-06-25 — "How campaign sending windows, time zones & pacing work" explainer # (why a Running campaign shows few sent early = paced for deliverability; why # the next-send time is shown in the campaign's chosen time zone). Covered by the # /documentation/* wildcard below; explicit entry helps future operators audit # what's intentionally crawlable. Allow: /documentation/how-campaign-sending-windows-and-time-zones-work # 2026-07-14 — "How campaign sending schedules & pacing work" explainer # (companion to the page above): the window you pick, even pacing across the # whole window, the daily limit (pause today → resume tomorrow), and why a # campaign may not be sending yet. Covered by the /documentation/* wildcard # below; explicit entry helps future operators audit what's intentionally # crawlable. Allow: /documentation/how-campaign-sending-schedule-and-pacing-works Allow: /documentation/why-was-this-prospect-skipped-bounce # 2026-07-24 — Two new customer-facing docs: the default-on follow-up threading # + single-sender affinity explainer, and the native-language warmup how-to. # Covered by the /documentation/* wildcard below; explicit entries help future # operators audit what's intentionally crawlable. Allow: /documentation/why-follow-ups-stay-in-the-same-thread-and-inbox Allow: /documentation/set-your-warmup-language Allow: /documentation/format-your-emails # 2026-07-25 — Two new customer-facing docs: attaching files to a Unified-Inbox # reply (campaign-email attachments stay deliberately unsupported), and combining # several conditions with AND/OR in one sequence step. Covered by the # /documentation/* wildcard below; explicit entries help future operators audit # what's intentionally crawlable. Allow: /documentation/how-do-i-attach-a-file-to-an-inbox-reply Allow: /documentation/how-do-i-combine-multiple-conditions-in-a-sequence # 2026-07-29 — "Why do verified emails still bounce?" — the honest-expectations # page for the email verifier: verification is point-in-time not a permanent # guarantee, what catch-all and unknown actually mean (and that unknown is free), # and what to do about each. Covered by the /documentation/* wildcard below; # explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/why-do-verified-emails-still-bounce Allow: /documentation/why-some-linkedin-prospects-show-unresolvable-url Allow: /documentation/how-to-personalize-linkedin-messages Allow: /documentation/how-to-see-the-linkedin-messages-you-sent Allow: /documentation/how-to-message-your-existing-linkedin-connections # 2026-07-03 — "Premium Unified Inbox" LinkedIn ship: five customer-facing guides # for the richer inbox (delivery/read receipts, attachments + voice notes, # reactions/edit/delete, mute + mark-unread, accept/decline received connection # requests). Covered by the /documentation/* wildcard below; explicit entries # help future operators audit what's intentionally crawlable. Allow: /documentation/see-when-your-linkedin-messages-are-delivered-and-read Allow: /documentation/send-attachments-and-voice-notes-in-linkedin-messages Allow: /documentation/react-to-edit-and-delete-linkedin-messages Allow: /documentation/mute-conversations-and-mark-them-unread Allow: /documentation/accept-or-decline-connection-requests-from-your-inbox # 2026-07-04 — Customer-facing guide: attach a file (PDF/image/one-pager/voice # note) to a LinkedIn campaign Send-message step; saved once, sent to every # prospect the step reaches. Covered by the /documentation/* wildcard below; # explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/attach-files-to-your-linkedin-campaign-messages # 2026-07-06 — "LinkedIn Tier-3" ship: four customer-facing guides — enrich a # prospect (a profile view that uses the safe daily number), publish/schedule # posts (profile or company page), post job openings + review applicants, and # check InMail credits + edit your LinkedIn profile. Covered by the # /documentation/* wildcard below; explicit entries help future operators audit # what's intentionally crawlable. Allow: /documentation/enrich-a-linkedin-prospect Allow: /documentation/publish-or-schedule-linkedin-posts Allow: /documentation/post-job-openings-and-review-applicants Allow: /documentation/check-inmail-credits-and-edit-your-linkedin-profile # 2026-07-06 — Instagram Add-On ship: six customer-facing guides for the new # Instagram DM outreach channel (connect an account, how outreach keeps the # account safe, build a DM campaign, why DMs land in message requests, daily & # hourly sending limits, managing the Instagram inbox). Covered by the # /documentation/* wildcard below; explicit entries help future operators audit # what's intentionally crawlable. Allow: /documentation/how-to-connect-your-instagram-account Allow: /documentation/how-instagram-outreach-keeps-your-account-safe Allow: /documentation/how-to-build-an-instagram-dm-campaign Allow: /documentation/why-some-instagram-dms-go-to-message-requests Allow: /documentation/instagram-daily-and-hourly-sending-limits Allow: /documentation/managing-your-instagram-inbox # 2026-07-12 — "How to build your Instagram audience": bring # your own handles (Instagram has no in-app prospect search) via CSV upload or by # pasting @handles in the campaign wizard. Covered by the /documentation/* # wildcard below; explicit entry helps future operators audit crawlability. Allow: /documentation/how-to-build-your-instagram-audience # 2026-08-26 — WhatsApp Add-On ship: four customer-facing guides for the new # WhatsApp channel (connect your number, how the sending limits keep the number # safe, run a campaign, build your audience). Covered by the /documentation/* # wildcard below; explicit entries help future operators audit what's # intentionally crawlable. Allow: /documentation/how-to-connect-your-whatsapp-number Allow: /documentation/how-whatsapp-sending-limits-keep-your-number-safe Allow: /documentation/how-to-run-a-whatsapp-campaign Allow: /documentation/how-to-build-your-whatsapp-audience # 2026-07-14 — "How to use your own tracking domain": point a # custom domain (track.yourdomain.com) at your open/click/unsubscribe links via one # CNAME → track.warmysender.com, verify, with automatic fallback to our default so a # broken/unset domain never stops sends. Covered by the /documentation/* wildcard # below; explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/how-to-use-your-own-tracking-domain # 2026-07-17 — "How to see emails that didn't get delivered": the Delivery Issues # view in the unified inbox left sidebar (Campaigns tab), splitting non-delivered # email sends into Bounced (address rejected) vs Couldn't send (message turned # away — usually temporary). Covered by the /documentation/* wildcard below; # explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/how-to-see-emails-that-didnt-get-delivered # 2026-07-19 — "How to redeem your AppSumo code": redemption-support how-to for # AppSumo lifetime-deal buyers (open WarmySender from AppSumo → Activate → sign # in with Google/Apple/one-time email code → plan unlocks instantly). Covered by # the /documentation/* wildcard below; explicit entry helps future operators # audit what's intentionally crawlable. Allow: /documentation/how-to-redeem-your-appsumo-code # 2026-06-16 — Customer-facing guide: why a multi-account LinkedIn campaign can # look like it's only using one account (Round Robin), and what a self-pause # means. Covered by the /documentation/* wildcard below; explicit entry helps # future operators audit what's intentionally crawlable. Allow: /documentation/why-is-my-linkedin-campaign-paused-or-only-using-one-account # 2026-06-19 — Accurate open & click tracking explainer (sender's own opens + # obvious automated/scanner opens excluded; per-campaign on/off toggle). # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/accurate-open-and-click-tracking # 2026-05-28 — Customer-facing explainer for LinkedIn reply notifications. # Covered by the /documentation/* wildcard below; explicit entry helps # future operators audit what's intentionally crawlable. Allow: /documentation/how-linkedin-reply-webhook-events-work # 2026-05-20 — Customer-facing explainer for the "accepted prospects stopped # getting follow-up messages" symptom. Covered by the /documentation/* # wildcard below; explicit entry helps future operators audit what's # intentionally crawlable. Allow: /documentation/why-some-prospects-stopped-after-accepting-on-linkedin # 2026-08-06 — Customer-facing explainer for the mirror-image symptom: a # LinkedIn sequence step that delivered the SAME message to one person more # than once (what a duplicate looks like, what now prevents it, how "Stop on # Reply" works and where it lives, and what to say to the prospect who got the # repeats). Covered by the /documentation/* wildcard below; explicit entry # helps future operators audit what's intentionally crawlable. Allow: /documentation/why-did-my-prospect-get-the-same-linkedin-message-twice # 2026-05-20 — Customer-facing explainer for the launch-time check that # names up to five affected prospects per missing custom variable, with the # three resolution paths (fill the data, remove the prospects, launch # anyway with auto-resume). Covered by the /documentation/* wildcard below; # explicit entry helps future operators audit what's intentionally # crawlable. Allow: /documentation/why-launch-shows-some-prospects-missing-template-data # 2026-05-20 — Customer-facing companion to the LinkedIn reconnect # escalating-reminders ship. Canonical landing destination for "why am I # getting this email?" questions when a LinkedIn session lapses. Covered # by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/why-am-i-getting-reconnect-emails-from-warmysender # 2026-05-20 — Microsoft 365 mailbox connection comprehensive guide. Allow: /documentation/connect-microsoft-365-mailbox # 2026-06-08 — Public REST API mailbox lifecycle reference (create/fetch/update/delete/restore). Allow: /documentation/managing-mailboxes-with-the-api # 2026-06-14 — Public REST API guide: create prospects + enroll them into a campaign. Allow: /documentation/create-and-enroll-prospects-with-the-api # 2026-05-21 — Gmail / Google Workspace alias-domain mailbox connection guide. Allow: /documentation/connect-gmail-workspace-alias # 2026-09-07 — Microsoft 365 / Exchange Online alias-mailbox connection guide # (several aliases on one licensed mailbox, each its own sender). Allow: /documentation/connect-microsoft-365-alias # 2026-06-10 — Gmail App Password "authentication failed on the first tries" # reassurance + fix guide (pasted-in spaces, Google's one-time security check, # wrong password). Complements the alias connection guide above. Allow: /documentation/gmail-app-password-says-auth-failed # 2026-05-20 — Threaded follow-up emails in multi-step campaigns guide. Allow: /documentation/how-do-i-send-follow-ups-in-the-same-email-thread # 2026-06-14 — Campaign sequence delays + conditions (YES/NO branching) guide. Allow: /documentation/how-to-set-up-campaign-sequences-delays-and-conditions # 2026-05-20 — How warmup ramps up customer-facing guide. Allow: /documentation/how-warmup-ramps-up # 2026-06-10 — How to control your warmup sending volume customer-facing guide. Allow: /documentation/how-to-control-your-warmup-sending-volume # 2026-06-18 — Email Verifier results explainer (Valid / Risky / Unknown / # Invalid). Covered by the /documentation/* wildcard below; explicit entry helps # future operators audit what's intentionally crawlable. Allow: /documentation/what-email-verification-results-mean # 2026-08-28 — Pre-send verification guide (why verify, why a stale list bounces, # what to do with Risky / Unknown). Covered by the /documentation/* wildcard below; # explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/do-i-need-to-verify-my-list-before-i-send # 2026-06-23 — Email Verifier limits & credits explainer (monthly verification # allowance, one credit per address, Unknown results are free, how to see what's # left, how to upgrade). Covered by the /documentation/* wildcard below; explicit # entry helps future operators audit what's intentionally crawlable. Allow: /documentation/email-verification-limits-and-credits # 2026-07-03 — Email Verifier PURCHASED credits explainer (buy verifications that # never expire and skip the daily pace; packs & prices; how to buy; credits vs # upgrade). Covered by the /documentation/* wildcard below; explicit entry helps # future operators audit what's intentionally crawlable. Allow: /documentation/email-verification-credits # 2026-08-05 — "Can I use the email verifier without a plan?" customer-facing doc # for the standalone-tool launch (the free daily check, buying credits with no # subscription, what a credit is spent on). Covered by the /documentation/* # wildcard below; explicit entry helps future operators audit what's # intentionally crawlable. Allow: /documentation/use-email-verifier-without-a-plan # 2026-08-12 — "What file formats can I upload for email verification?" # customer-facing doc (any spreadsheet export works, no "email" column needed, # semicolon/tab/pipe separators detected, per-file address and size limits, # duplicates removed). Covered by the /documentation/* wildcard below; explicit # entry helps future operators audit what's intentionally crawlable. Allow: /documentation/what-file-formats-can-i-upload-for-email-verification # 2026-09-01 — "Does email verification keep my contact names, companies and # custom columns?" customer-facing doc (results download now appends every # uploaded column after the verification columns; lookup-merge recipe for older # downloads). Covered by the /documentation/* wildcard below; explicit entry # helps future operators audit what's intentionally crawlable. Allow: /documentation/does-email-verification-keep-my-contact-data # 2026-09-05 — "Why is my warmup daily limit lower than my target?" customer-facing # doc (the daily warmup limit is a ramp that grows every two days, per-strategy # start and ceiling, every reason line the product now shows next to the limit, # how to switch strategy in-app or via an AI agent). Covered by the # /documentation/* wildcard below; explicit entry helps future operators audit # what's intentionally crawlable. Allow: /documentation/why-is-my-warmup-daily-limit-lower-than-my-target # 2026-09-06 — THE CANONICAL warmup daily-volume page. Absorbs the eight-URL # "why is warmup sending fewer emails than I set" cluster; the seven retired # slugs (the line above among them) 301 here and stay Allow-listed on purpose, # so a crawler can fetch them and see the redirect. Allow: /documentation/how-your-warmup-daily-volume-is-decided # 2026-06-18 — "What happened to the Business plan?" customer-facing doc (plan # sunset — discontinued for new customers; existing customers grandfathered). # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/what-happened-to-the-business-plan # 2026-06-14 — "Why adding sending days didn't increase my volume" customer-facing # guide (queued emails keep their dates; one-click Rebalance fills the new days). Allow: /documentation/why-adding-sending-days-didnt-increase-volume # 2026-06-14 — How to use your existing contacts in a new campaign customer-facing guide. Allow: /documentation/reuse-existing-contacts-in-a-new-campaign # 2026-07-12 — Getting-started / product-tour guide (4 pillars + how to take and # replay the 60-second guided tour). Covered by the /documentation/* wildcard # below; explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/getting-started-product-tour # 2026-06-03 — Understanding your warmup Inbox Rate customer-facing guide. Allow: /documentation/understanding-your-warmup-inbox-rate Allow: /documentation/why-warmup-emails-appear-in-your-inbox # 2026-07-27 — "Why warmup emails appear in your Sent folder" guide (the # customer's own provider keeps a copy of everything sent, so warmup shows up in # Sent even though we never file it there; one [ref: subject filter hides it). Allow: /documentation/why-warmup-emails-appear-in-your-sent-folder # 2026-07-27 — "How to cancel your subscription or delete your account" guide. # The URL llms.txt already hands AI assistants for that question; explicitly # crawlable so the answer comes from us rather than being guessed at. Allow: /documentation/cancel-or-delete-your-account # 2026-07-22 — "Why won't my LinkedIn account connect?" reassurance + # how-to guide (a failed attempt is a brief busy moment; seat/billing/account # unaffected; the three connection methods + verification codes explained). Allow: /documentation/why-wont-my-linkedin-account-connect # 2026-08-28 — "What happens to my campaigns when I reconnect LinkedIn?" — # campaigns, prospects and each prospect's place in the sequence follow the new # connection automatically; the daily/weekly allowance carries over on purpose; # running campaigns pause for a quick review; and what the "needs relinking" # note means, with its fix. Allow: /documentation/what-happens-to-my-campaigns-when-i-reconnect-linkedin # 2026-06-07 — Warmup shows active but no emails arriving ("Incoming warmup # catching up") customer-facing reassurance guide. Allow: /documentation/warmup-shows-active-but-no-emails-arriving # 2026-08-13 — What warmup's receiving states mean. Reference page for the # "Not receiving warmup", "Incoming warmup paused" and "Cooling down" notes, # and why the Success Rate figure (a sending score) is unaffected by them. Allow: /documentation/what-warmup-receiving-states-mean # 2026-08-06 — "Why is incoming warmup paused on my inbox?" — what the note # means, that outbound sending is unaffected, and the difference between a # short pause that lifts by itself and one that needs a review from us. Allow: /documentation/why-is-incoming-warmup-paused-on-my-inbox # 2026-08-10 — "My inbox rate looks great but I'm not receiving warmup emails" — # the third page in the incoming-warmup family: the headline score measures the # warmup this mailbox SENT and where it landed, so a high score and a mailbox # receiving nothing are both true at once. Allow: /documentation/my-inbox-rate-is-high-but-no-warmup-emails-are-arriving # 2026-08-12 — "Why warmup emails aren't arriving in my inbox — and how to fix # it" — the fourth page in the incoming-warmup family and the only one that # covers a receiving problem the customer has to fix: a domain with no # mail-delivery setting, a filter moving warmup out of the inbox, or an address # with no mailbox behind it. Includes the two-minute check that separates those # from the passing kind that clears on its own. Allow: /documentation/why-warmup-emails-are-not-arriving-in-my-inbox # 2026-08-19 — "Why can't WarmySender read my inbox?" The fourth cause the page # above was missing, and the one that stranded a customer for three weeks: # sending and reading are two separately granted permissions on a Microsoft 365 # or Google Workspace mailbox, so an admin can allow sending and block reading — # warmup then sends perfectly and can measure nothing. Carries the exact admin # click-path for both providers. Covered by the /documentation/* wildcard below; # listed explicitly so a future operator auditing this file can see it. Allow: /documentation/why-we-cannot-read-your-inbox # 2026-08-20 — "Why did my campaign pause for bounces?" The customer-question # page for the automatic bounce-rate pause. The same protection was documented # three times before this, but only under feature names in the help hub # ("Bounce Shield Protection", "Campaign in cooldown mode", "Campaign Safety & # Cooldown"), so the search people actually run — "why did my campaign pause" — # had nothing to land on. Covered by the /documentation/* wildcard below; listed # explicitly so a future operator auditing this file can see it. Allow: /documentation/why-did-my-campaign-pause-for-bounces # 2026-09-12 — "Edit a contact's fields, tags and custom fields". Editing a saved # contact now offers the same full field set as adding one (website, country, # city, industry, tags and brand-new custom fields), in the app, through the # public API and via a connected AI agent. Covered by the /documentation/* # wildcard below; listed explicitly so a future operator auditing this file can # see it. Allow: /documentation/edit-a-contacts-fields-tags-and-custom-fields # 2026-08-12 — "How do I switch my LinkedIn seats to annual billing?" — moving # seats already owned onto annual or 3-year billing, adding seats on a longer # term in the same step, and the rule that a seat term can never outrun the # plan's term. Covered by the /documentation/* wildcard below; listed explicitly # so a future operator can see it is intentionally crawlable. Allow: /documentation/how-do-i-switch-my-linkedin-seats-to-annual-billing # 2026-08-10 — "Why did my LinkedIn invites pause today?" — LinkedIn signalled a # limit, the account is resting to stay safe, sending restarts by itself; plus # why a week can total far fewer invitations than the number configured. Allow: /documentation/why-did-my-linkedin-invites-pause-today # 2026-06-09 — "Why are my mailboxes reconnecting" calm reassurance guide # (temporary provider-side connection hiccup; warmup auto-resumes). Allow: /documentation/why-are-my-mailboxes-reconnecting # 2026-07-18 — "What is my mailbox's warmup score?" explainer (what the warmup # score means, why a new mailbox shows "Building data", why it recovers on its own). Allow: /documentation/what-is-my-mailbox-warmup-score # 2026-07-18 — "How are my campaign metrics calculated?" explainer (Open Rate, # Click Rate, Reply Rate, Bounce Rate explained plainly; open rate is # approximate; click rate is measured against emails sent; reply rate is the # number to optimize; sequences focus on replies). Allow: /documentation/how-are-my-campaign-metrics-calculated # 2026-07-16 — "Why is my mailbox full?" storage explainer (mailbox ran out of # room with the provider — storage, not reputation/spam and not a blocked # domain; warmup pauses while nothing can be delivered; WarmySender removes # warmup mail after about a day so it stops consuming space; customer frees up # space or raises the mailbox's storage). Allow: /documentation/why-is-my-mailbox-full # 2026-06-26 — "Many mailboxes on one hosting account show Reconnect / Auth # Error" shared-host explainer (host briefly limits simultaneous connections; # WarmySender paces + distinguishes busy-host from a real password problem + # auto-recovers). Allow: /documentation/many-mailboxes-on-one-hosting-account-show-reconnect # 2026-06-19 — "Why your warmup can pause — and how it resumes" calm reassurance # guide (warmup briefly pauses to protect sending reputation after a temporary # delivery issue; mailbox + progress safe; one-click resume; recovers on its own). Allow: /documentation/why-your-warmup-can-pause # 2026-08-05 — "Why did my warmup volume go down?" explainer (warmup # keeps running but at a smaller daily amount because some of the mailbox's # warmup mail landed in spam; separates "we're still building a picture of this # mailbox" from "this mailbox really is landing in spam"; lifts on its own). # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/why-did-my-warmup-volume-go-down # 2026-06-18 — Affiliate program customer-facing guide. Covered by the # /documentation/* wildcard below; explicit entry helps future operators # audit what's intentionally crawlable. Allow: /documentation/how-the-warmysender-affiliate-program-works # 2026-06-19 — Why warmup shows only a few emails early in the day (within-day # pacing + gradual ramp) customer-facing guide. Allow: /documentation/why-warmup-shows-few-emails-early-in-the-day # 2026-07-05 — Why warmup emails are spread through the day (not one burst) # natural-pacing explainer. Same daily amount, paced like a real person to # protect sender reputation. Covered by the /documentation/* wildcard below; # explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/why-warmup-emails-are-spread-through-the-day # 2026-07-22 — Why is my warmup bounce rate high (small-sample effect: a high- # looking bounce rate on a small early/ramping sample, warmup skips undeliverable # inboxes before sending, and when to actually act). Covered by the /documentation/* # wildcard below; explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/why-is-my-warmup-bounce-rate-high # 2026-06-01 — Why a new LinkedIn account starts slow / ramps up over the # first few weeks, and why free accounts send note-free connection requests. # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/why-your-new-linkedin-account-starts-slow # 2026-06-23 — How WarmySender protects your LinkedIn account: stays inside # LinkedIn's safe daily/weekly limits, paces sending gradually, auto-slows or # pauses before risky volume, temporary-restriction guidance + best practices. # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/how-warmysender-protects-your-linkedin-account # 2026-06-09 — LinkedIn sending limits & account tiers reference (Free / # Premium / Sales Navigator / Recruiter): the two limits that apply, the # free-account with-a-note monthly cap, InMail availability, and the ramp. # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/linkedin-sending-limits-and-account-tiers # 2026-05-28 — Customer-facing explainer for "rejected by recipient mail # server" campaign results. Covered by the /documentation/* wildcard below; # explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/why-emails-are-being-rejected # 2026-09-05 — Companion explainer for the campaign that paused with "messages # were rejected": the customer's own email host refused the message on its # outgoing spam filter, so the remedy is the message, never the contact list. # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/why-were-my-emails-rejected-as-spam-before-sending # 2026-06-22 — "Why is my campaign 'running' but no emails sent yet?" reassurance # explainer (cold-email campaigns pace sends across the sending window; first # emails start within a couple of minutes of launch). Covered by the # /documentation/* wildcard below; explicit entry helps future operators audit # what's intentionally crawlable. Allow: /documentation/why-is-my-campaign-running-but-no-emails-sent-yet # 2026-08-04 — "Campaign says Running but never sends any emails" — the # PERSISTENT counterpart to the page above (hours or days, nothing ever sent, # next-send time keeps sliding). Headline cause: every step in the sequence is # switched off, so the campaign has nothing to send and waits while still # reading Running. Also covers the legitimate waits (outside the sending window, # daily limit reached, spacing between sends, no connected mailbox, future start # date, nobody eligible to email). Covered by the /documentation/* wildcard # below; explicit entry helps future operators audit what's intentionally # crawlable. Allow: /documentation/campaign-says-running-but-never-sends-any-emails # 2026-05-28 (Wave 3) — Evergreen leaderboard + benchmark pages. The /blog/* # wildcard above already covers these, and /documentation/* covers the # methodology companions, but explicit entries help future operators audit # what's intentionally crawlable and make the AI-crawlability checklist # survey-able by grep. Allow: /blog/best-cold-email-tools Allow: /blog/best-email-warmup-tools Allow: /blog/best-linkedin-automation-tools Allow: /blog/best-instagram-growth-tools Allow: /blog/email-deliverability-benchmarks Allow: /documentation/cold-email-tools-benchmark-methodology Allow: /documentation/email-warmup-benchmark-methodology Allow: /documentation/linkedin-tools-benchmark-methodology Allow: /documentation/deliverability-benchmark-methodology # 2026-06-23 — Three new customer-facing self-serve guides. The /documentation/* # wildcard below already covers these single-segment slugs; explicit entries # help future operators audit what's intentionally crawlable and keep the # AI-crawlability checklist grep-survey-able. Allow: /documentation/your-campaign-draft-is-saved-automatically Allow: /documentation/why-a-prospect-was-marked-bounced Allow: /documentation/why-an-inbox-shows-temporary-provider-slowdown # 2026-06-24 — "My sending domain shows on a blocklist" vendor-neutral explainer. # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/my-sending-domain-shows-on-a-blocklist # 2026-06-24 — "Connecting mailboxes that don't use an App Password (hosting / # IMAP providers)" guide: most providers other than Gmail/Outlook connect with # the customer's normal mailbox password (no App Password, no 2FA). Covered by # the /documentation/* wildcard below; explicit entry helps future operators # audit what's intentionally crawlable. Allow: /documentation/connecting-mailboxes-without-app-passwords # 2026-06-26 — "Connect WarmySender to Claude" guide: add the assistant # connector (web + desktop), the two sign-in options, and the #1 fix for a # greyed-out connector (sign in to warmysender.com first, then re-authorize). # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/connect-warmysender-to-claude # 2026-07-28 — "Connecting an AI agent that asks you to sign in": the custom- # connector / sign-in path end to end, and what to do if the connection doesn't # complete (it used to return people to their dashboard — now fixed). # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/connecting-an-ai-agent-that-asks-you-to-sign-in # 2026-07-02 — "Why did my LinkedIn account disconnect after I canceled my # seat?" explainer: canceling a seat safely pauses the connected account # (reversible; 7-day instant-restore grace; campaigns + progress preserved). # Covered by the /documentation/* wildcard below; explicit entry helps future # operators audit what's intentionally crawlable. Allow: /documentation/linkedin-account-paused-after-seat-cancelled # 2026-07-03 — "What happens when someone accepts my LinkedIn invite late?" # landing page for the per-campaign "Re-engage late accepts" setting (default # off → Late Accepts list; on → auto-continue). Covered by the /documentation/* # wildcard below; explicit entry helps future operators audit what's intentionally # crawlable. Allow: /documentation/what-happens-when-someone-accepts-my-linkedin-invite-late # 2026-07-03 — "Reconnecting a LinkedIn account and your campaigns": reconnecting # a restricted/disconnected account keeps campaigns working (they stay pointed at # the reconnected account and resume automatically). Covered by the # /documentation/* wildcard below; explicit entry helps future operators audit # what's intentionally crawlable. Allow: /documentation/reconnecting-a-linkedin-account-and-your-campaigns # 2026-07-04 — Three new self-serve docs: why a Sales Navigator list won't import # (rewritten 2026-07-07 — lists import when the connected account is carrying # Sales Navigator access; after a reconnect an account can come back without that # access even though the subscription is active and may show Premium; one-click # "Re-check Sales Navigator access" restores it; reconnect with Sales Navigator # open in the browser if the re-check can't find it; regular search links work on # any account); why LinkedIn-imported leads aren't getting emails (no email # address on the record, so email steps are skipped — add emails by importing a # list that already includes them, or by saving contacts from the leads # database, where the address is revealed on save); and safe cold-email sending # limits after warmup (per-provider # daily volume, ongoing warmup ratio, warmup duration, reputation floor). Covered # by the /documentation/* wildcard below; explicit entries help future operators # audit what's intentionally crawlable. Allow: /documentation/why-my-sales-navigator-list-wont-import Allow: /documentation/why-my-linkedin-imported-leads-arent-getting-emails Allow: /documentation/safe-cold-email-sending-limits-after-warmup # 2026-08-03 — the honest answer to "how do I get emails for these people?": the # leads database (searching is free and results stay masked; the address is # revealed when you save a contact) or importing a list that already includes # the addresses. Also states plainly that address verification CHECKS an address # you already have rather than discovering a missing one, and that there is no # per-profile lookup for an arbitrary imported contact. Covered by the # /documentation/* wildcard below; the explicit entry helps future operators # audit what's intentionally crawlable. Allow: /documentation/how-do-i-get-email-addresses-for-my-contacts # 2026-07-06 — Connect any AI agent (Claude, ChatGPT, Cursor, Codex, OpenClaw, # Hermes Agent) to run your whole outreach in plain language. Covered by the # /documentation/* wildcard below; explicit entry helps operators audit crawlability. Allow: /documentation/connect-your-ai-agent # 2026-09-09 — "Connect WarmySender to Muse Code": Meta's terminal coding agent, # connected with a workspace key (it has no sign-in screen for MCP servers). # Covered by the /documentation/* wildcard below; explicit entry helps operators # audit crawlability. Allow: /documentation/connect-warmysender-to-muse-code Allow: /documentation/run-cold-email-outreach-with-meta-muse-code Allow: /documentation/can-meta-muse-run-my-outreach # 2026-07-22 — Run your outreach on autopilot with AI via the MCP server: connect # any MCP AI client (Claude, ChatGPT, Cursor, Windsurf, Zed, Codex, Perplexity) and # automate cold email + LinkedIn + Instagram by chatting. Covered by the # /documentation/* wildcard below; explicit entry helps operators audit crawlability. Allow: /documentation/automate-outreach-with-ai # 2026-07-09 — Four customer-facing self-serve docs: filter the leads database by # industry (pick a grouped ★ industry option that matches across data sources); # why warmup + auto-stop-on-reply need incoming (IMAP) access; email-verification # monthly allowance vs. purchased credit packs (verify a big list the same day, # safely, alongside campaigns); and why every campaign email includes an # unsubscribe link. Covered by the /documentation/* wildcard below; explicit # entries help future operators audit what's intentionally crawlable. Allow: /documentation/filtering-leads-by-industry # 2026-09-02 — location filters in the leads database: City matches any # capitalization and common short forms (NYC = New York), a Postcode / ZIP # prefix filter and a "Street contains" filter (US + Canada), a "Verified emails # only" switch, and "Did you mean ...?" suggestions. Covered by the # /documentation/* wildcard below; explicit entry for auditability. Allow: /documentation/how-to-filter-leads-by-postcode-city-and-street Allow: /documentation/why-warmup-needs-imap-incoming-access Allow: /documentation/email-verification-credits-and-daily-limits Allow: /documentation/unsubscribe-link-in-campaign-emails # 2026-09-10 (GL#709) — the answer to "my records read as valid, my mailboxes read # as healthy, I have zero bounces, and my mail still goes to spam": the domain is # delegated to two sets of nameservers at once and one of them is stale, so # authentication passes for the receivers that ask one pair and fails for those # that ask the other — or the domain has stopped resolving altogether, in which # case "add your records" is the wrong advice because there is nowhere to publish # them. Covered by the /documentation/* wildcard below; explicit entry for # auditability. Allow: /documentation/why-my-mail-goes-to-spam-when-my-records-look-correct # 2026-07-10 — Two customer-facing self-serve docs: why a cold email campaign can # finish with 0 sent (every contact was on the suppression list — unsubscribed / # bounced / do-not-contact; common when testing with your own address after # clicking your own unsubscribe link; expected, not a bug); and what happens to # LinkedIn seats + connected accounts if a payment fails (seats pause + accounts # set aside; ~1-week grace preserves logins + progress; paying restores # everything automatically). Covered by the /documentation/* wildcard below; # explicit entries help future operators audit what's intentionally crawlable. Allow: /documentation/why-did-my-campaign-finish-without-sending Allow: /documentation/linkedin-seats-after-a-failed-payment # 2026-07-11 — Two customer-facing self-serve docs: how to apply a cleaned / # verified list to a running campaign without restarting it or double-emailing # anyone (the clean "- Verified" list is ready in-app, "Use in campaign" opens # the builder preselected, already-contacted people are skipped, Invalid # addresses are set aside); and safe daily cold-email volume after warmup per # provider (Gmail / Outlook / Yahoo ranges, keep warmup running alongside cold, # ~4-6 weeks to warmed, warmup mail tagged + auto-tidied, per-domain spam-rate # auto-slowdown). Covered by the /documentation/* wildcard below; explicit # entries help future operators audit what's intentionally crawlable. Allow: /documentation/apply-verified-list-to-campaign-without-duplicates Allow: /documentation/how-to-save-only-confirmed-addresses-from-verification Allow: /documentation/safe-daily-cold-email-volume-after-warmup # 2026-07-13 — How warmup protects your deliverability: warmup # automatically avoids sending to inboxes that aren't accepting mail, on the # first message and every follow-up reply, and never counts those skipped sends # against your mailbox. Covered by the /documentation/* wildcard below; explicit # entry helps future operators audit what's intentionally crawlable. Allow: /documentation/how-warmup-protects-your-deliverability # 2026-07-21 — Why is my contact count higher than my lists? Explainer for the new # "Not in a list" view: every contact counts toward your plan's contact limit # whether or not it's in a list, and some contacts (most often LinkedIn imports) # are added without a list; open "Not in a list" on the Prospects page to organize, # remove, or upgrade. Covered by the /documentation/* wildcard below; explicit # entry helps future operators audit what's intentionally crawlable. Allow: /documentation/why-is-my-contact-count-higher-than-my-lists # 2026-09-01 — How automatic replies and out-of-office messages are handled. An # auto-reply is not a reply: it never stops the sequence and never counts in the # reply rate. Also documents the two recovery paths when one slips through # ("Resume sequence" on the campaign's Prospects tab, or relabelling the message # "Auto-Reply / Out of Office" in the Inbox) and the guarantee that resuming # continues from the next unsent step. Covered by the /documentation/* wildcard # below; explicit entry helps future operators audit what's intentionally crawlable. Allow: /documentation/does-an-out-of-office-reply-stop-my-campaign # 2026-09-06 — Documentation child of /unified-inbox: what exactly stops on a # reply, why an automatic reply does not, and how to resume a sequence that # stopped by mistake. Covered by the /documentation/* wildcard below; explicit # entry helps future operators audit what's intentionally crawlable. Allow: /documentation/how-stop-on-reply-works-across-channels # 2026-09-15 — Second documentation child of /unified-inbox: what appears in the # inbox and what does not, the Sync summary broken down, where bounces go, and # what to do when a colleague replies instead of the prospect. Covered by the # /documentation/* wildcard below; explicit entry helps future operators audit # what's intentionally crawlable. Allow: /documentation/why-do-i-only-see-some-replies-in-my-inbox Allow: /documentation/* Allow: /docs/integrations Allow: /mcp Allow: /ai-agents # 2026-09-09 — Real agent use-case gallery (index + one page per agent, e.g. # /ai-agents/use-cases/claude). Allow: /ai-agents/use-cases Allow: /ai-agents/use-cases/* # AI-agents + LinkedIn lead-magnet landing page (2026-08-29) — indexed and in # the sitemap. Its companion playbook page is deliberately disallowed below. Allow: /ai-agents-linkedin-leads Allow: /authors Allow: /authors/* # Locale-prefixed routes (es, fr, de, pt-BR, ja, zh-CN, ko, it, nl, ar) # Spanish (es) locale routes Allow: /es/blog Allow: /es/blog/* Allow: /es/blog/posts/* Allow: /es/blog/use-cases Allow: /es/blog/use-cases/* Allow: /es/blog/integrations Allow: /es/blog/integrations/* Allow: /es/blog/features Allow: /es/blog/features/* Allow: /es/blog/compare Allow: /es/blog/compare/* Allow: /es/blog/guides Allow: /es/blog/guides/* Allow: /es/blog/glossary Allow: /es/blog/glossary/* Allow: /es/blog/cold-email Allow: /es/blog/cold-email/* Allow: /es/blog/deliverability Allow: /es/blog/deliverability/* Allow: /es/blog/linkedin-outreach Allow: /es/blog/linkedin-outreach/* # French (fr) locale routes Allow: /fr/blog Allow: /fr/blog/* Allow: /fr/blog/posts/* Allow: /fr/blog/use-cases Allow: /fr/blog/use-cases/* Allow: /fr/blog/integrations Allow: /fr/blog/integrations/* Allow: /fr/blog/features Allow: /fr/blog/features/* Allow: /fr/blog/compare Allow: /fr/blog/compare/* Allow: /fr/blog/guides Allow: /fr/blog/guides/* Allow: /fr/blog/glossary Allow: /fr/blog/glossary/* Allow: /fr/blog/cold-email Allow: /fr/blog/cold-email/* Allow: /fr/blog/deliverability Allow: /fr/blog/deliverability/* Allow: /fr/blog/linkedin-outreach Allow: /fr/blog/linkedin-outreach/* # German (de) locale routes Allow: /de/blog Allow: /de/blog/* Allow: /de/blog/posts/* Allow: /de/blog/use-cases Allow: /de/blog/use-cases/* Allow: /de/blog/integrations Allow: /de/blog/integrations/* Allow: /de/blog/features Allow: /de/blog/features/* Allow: /de/blog/compare Allow: /de/blog/compare/* Allow: /de/blog/guides Allow: /de/blog/guides/* Allow: /de/blog/glossary Allow: /de/blog/glossary/* Allow: /de/blog/cold-email Allow: /de/blog/cold-email/* Allow: /de/blog/deliverability Allow: /de/blog/deliverability/* Allow: /de/blog/linkedin-outreach Allow: /de/blog/linkedin-outreach/* # Portuguese Brazil (pt-BR) locale routes Allow: /pt-BR/blog Allow: /pt-BR/blog/* Allow: /pt-BR/blog/posts/* Allow: /pt-BR/blog/use-cases Allow: /pt-BR/blog/use-cases/* Allow: /pt-BR/blog/integrations Allow: /pt-BR/blog/integrations/* Allow: /pt-BR/blog/features Allow: /pt-BR/blog/features/* Allow: /pt-BR/blog/compare Allow: /pt-BR/blog/compare/* Allow: /pt-BR/blog/guides Allow: /pt-BR/blog/guides/* Allow: /pt-BR/blog/glossary Allow: /pt-BR/blog/glossary/* Allow: /pt-BR/blog/cold-email Allow: /pt-BR/blog/cold-email/* Allow: /pt-BR/blog/deliverability Allow: /pt-BR/blog/deliverability/* Allow: /pt-BR/blog/linkedin-outreach Allow: /pt-BR/blog/linkedin-outreach/* # Japanese (ja) locale routes Allow: /ja/blog Allow: /ja/blog/* Allow: /ja/blog/posts/* Allow: /ja/blog/use-cases Allow: /ja/blog/use-cases/* Allow: /ja/blog/integrations Allow: /ja/blog/integrations/* Allow: /ja/blog/features Allow: /ja/blog/features/* Allow: /ja/blog/compare Allow: /ja/blog/compare/* Allow: /ja/blog/guides Allow: /ja/blog/guides/* Allow: /ja/blog/glossary Allow: /ja/blog/glossary/* Allow: /ja/blog/cold-email Allow: /ja/blog/cold-email/* Allow: /ja/blog/deliverability Allow: /ja/blog/deliverability/* Allow: /ja/blog/linkedin-outreach Allow: /ja/blog/linkedin-outreach/* # Chinese Simplified (zh-CN) locale routes Allow: /zh-CN/blog Allow: /zh-CN/blog/* Allow: /zh-CN/blog/posts/* Allow: /zh-CN/blog/use-cases Allow: /zh-CN/blog/use-cases/* Allow: /zh-CN/blog/integrations Allow: /zh-CN/blog/integrations/* Allow: /zh-CN/blog/features Allow: /zh-CN/blog/features/* Allow: /zh-CN/blog/compare Allow: /zh-CN/blog/compare/* Allow: /zh-CN/blog/guides Allow: /zh-CN/blog/guides/* Allow: /zh-CN/blog/glossary Allow: /zh-CN/blog/glossary/* Allow: /zh-CN/blog/cold-email Allow: /zh-CN/blog/cold-email/* Allow: /zh-CN/blog/deliverability Allow: /zh-CN/blog/deliverability/* Allow: /zh-CN/blog/linkedin-outreach Allow: /zh-CN/blog/linkedin-outreach/* # Korean (ko) locale routes Allow: /ko/blog Allow: /ko/blog/* Allow: /ko/blog/posts/* Allow: /ko/blog/use-cases Allow: /ko/blog/use-cases/* Allow: /ko/blog/integrations Allow: /ko/blog/integrations/* Allow: /ko/blog/features Allow: /ko/blog/features/* Allow: /ko/blog/compare Allow: /ko/blog/compare/* Allow: /ko/blog/guides Allow: /ko/blog/guides/* Allow: /ko/blog/glossary Allow: /ko/blog/glossary/* Allow: /ko/blog/cold-email Allow: /ko/blog/cold-email/* Allow: /ko/blog/deliverability Allow: /ko/blog/deliverability/* Allow: /ko/blog/linkedin-outreach Allow: /ko/blog/linkedin-outreach/* # Italian (it) locale routes Allow: /it/blog Allow: /it/blog/* Allow: /it/blog/posts/* Allow: /it/blog/use-cases Allow: /it/blog/use-cases/* Allow: /it/blog/integrations Allow: /it/blog/integrations/* Allow: /it/blog/features Allow: /it/blog/features/* Allow: /it/blog/compare Allow: /it/blog/compare/* Allow: /it/blog/guides Allow: /it/blog/guides/* Allow: /it/blog/glossary Allow: /it/blog/glossary/* Allow: /it/blog/cold-email Allow: /it/blog/cold-email/* Allow: /it/blog/deliverability Allow: /it/blog/deliverability/* Allow: /it/blog/linkedin-outreach Allow: /it/blog/linkedin-outreach/* # Dutch (nl) locale routes Allow: /nl/blog Allow: /nl/blog/* Allow: /nl/blog/posts/* Allow: /nl/blog/use-cases Allow: /nl/blog/use-cases/* Allow: /nl/blog/integrations Allow: /nl/blog/integrations/* Allow: /nl/blog/features Allow: /nl/blog/features/* Allow: /nl/blog/compare Allow: /nl/blog/compare/* Allow: /nl/blog/guides Allow: /nl/blog/guides/* Allow: /nl/blog/glossary Allow: /nl/blog/glossary/* Allow: /nl/blog/cold-email Allow: /nl/blog/cold-email/* Allow: /nl/blog/deliverability Allow: /nl/blog/deliverability/* Allow: /nl/blog/linkedin-outreach Allow: /nl/blog/linkedin-outreach/* # Arabic (ar) locale routes Allow: /ar/blog Allow: /ar/blog/* Allow: /ar/blog/posts/* Allow: /ar/blog/use-cases Allow: /ar/blog/use-cases/* Allow: /ar/blog/integrations Allow: /ar/blog/integrations/* Allow: /ar/blog/features Allow: /ar/blog/features/* Allow: /ar/blog/compare Allow: /ar/blog/compare/* Allow: /ar/blog/guides Allow: /ar/blog/guides/* Allow: /ar/blog/glossary Allow: /ar/blog/glossary/* Allow: /ar/blog/cold-email Allow: /ar/blog/cold-email/* Allow: /ar/blog/deliverability Allow: /ar/blog/deliverability/* Allow: /ar/blog/linkedin-outreach Allow: /ar/blog/linkedin-outreach/* # Private app routes — authenticated-only, zero search value. # Repeated in every user-agent group on purpose: named bots ignore "User-agent: *". Disallow: /dashboard Disallow: /mailboxes Disallow: /warmup Disallow: /campaigns Disallow: /sequences Disallow: /prospects Disallow: /contacts Disallow: /templates Disallow: /inbox Disallow: /analytics Disallow: /settings Disallow: /billing Disallow: /admin Disallow: /audiences Disallow: /linkedin Disallow: /whatsapp Disallow: /instagram Disallow: /hire-us Disallow: /affiliate$ Disallow: /login Disallow: /review-login Disallow: /register Disallow: /invite/ Disallow: /auth/ Disallow: /appsumo/ Disallow: /feedback/ # In-app support system (2026-09-09, docs/SUPPORT-SYSTEM-PRD.md): the ask form # and a customer's own ticket list/threads are private. The public board # (/support/questions, /support/questions/) and /support/status are # allowed below; longest-match keeps these two Disallows from touching them. Disallow: /support/new Disallow: /support/tickets # Unlisted lead-magnet playbook (2026-08-29) — reachable only via the email # people receive; the indexed capture page is /ai-agents-linkedin-leads. This # longer path wins over the shorter "Allow: /ai-agents" per longest-match, and # it does NOT shadow /ai-agents or /ai-agents-linkedin-leads. Disallow: /ai-agents-linkedin-playbook # Public, machine-readable API spec (OpenAPI 3.1) stays fetchable — longest # matching rule wins, so this Allow beats the Disallow below for that one path. Allow: /api/v1/openapi.json Disallow: /api/ # The index plus every shard it points at. Listing the shards directly is # belt-and-braces: a crawler that never follows the still finds # all five URL lists, and Bing/IndexNow-side tooling reads shards it is told # about. Keep this list in step with the shard routes in server/sitemap.ts. Sitemap: https://warmysender.com/sitemap.xml Sitemap: https://warmysender.com/sitemap-static.xml Sitemap: https://warmysender.com/sitemap-blog.xml Sitemap: https://warmysender.com/sitemap-features.xml Sitemap: https://warmysender.com/sitemap-comparisons.xml Sitemap: https://warmysender.com/sitemap-glossary.xml