First commit

research/landingpage-best-practices-handover.yaml

@@ -0,0 +1,158 @@
+goal: >
+  Prepare a concise research handover for turning Bay Area Email Services into a separate
+  marketing/Product-Led landing page that can later support SaaS positioning.
+current_phase: >
+  research
+owner: >
+  swarm-researcher
+context:
+  - The separate project folder already exists at C:/Users/a931627/Documents/gitea/bayarea/E-Mail Webseite Marketing.
+  - Existing project content positions the offer as local Corpus Christi business email setup/support plus a distinct Bay Area Email Services hosting offer.
+  - Current core offer from local materials: 25 GB business mailbox, $5 per inbox, domain email, DNS setup for MX/SPF/DKIM/DMARC, migration, spam filtering, aliases/forwards/auto-replies, Outlook/mobile setup, and local support.
+  - Infrastructure positioning from existing materials: AWS-based platform, inbound S3 buffering before delivery, outbound Amazon SES, hot standby failover, DNS/migration/day-to-day management handled locally.
+  - Google Workspace Business Starter is a relevant comparison anchor: custom business email, 30 GB pooled storage per user, listed at $7/user/month on annual billing in the checked US-facing page.
+  - Microsoft 365 Business Basic is a relevant comparison anchor: custom business email plus web/mobile Office apps, Teams, OneDrive, spam/malware filtering, listed at $6/user/month paid yearly on the checked US-facing page.
+  - AWS SES documentation supports claims around deliverability insights, configuration recommendations, and SPF/DKIM/DMARC support, but not a blanket guarantee that every message reaches inboxes.
+  - AWS S3 Standard documentation supports a factual durability/availability claim for objects stored in S3, but that should not be converted into an email-platform uptime guarantee unless the service has its own SLA.
+  - Google SEO guidance favors descriptive URLs, helpful reliable people-first content, and structured data where it accurately describes the page/business.
+recommended_sections:
+  - id: hero
+    purpose: >
+      State the product-level promise before listing infrastructure.
+    content_direction:
+      - "Headline option: Business email that stays professional, deliverable, and locally supported."
+      - "Subcopy should combine domain email, DNS correctness, migration, and local Corpus Christi support."
+      - "Primary CTA: Get email set up / Book assessment. Secondary CTA: Compare plans or See how migration works."
+    decision_points:
+      - Decide whether "$5 per inbox" appears in the hero or in the pricing band; hero price is strong for product-led positioning, but may attract low-intent buyers if setup/support is the real margin.
+  - id: problem
+    purpose: >
+      Name the business pain in non-technical terms before introducing SPF/DKIM/DMARC.
+    content_direction:
+      - "Missed leads from spam-folder delivery."
+      - "Unprofessional free Gmail/Yahoo addresses."
+      - "Downtime or lockouts from old/shared hosting email."
+      - "No clear local support when email breaks."
+  - id: product_snapshot
+    purpose: >
+      Make the offer scannable as a product, not only a consulting service.
+    content_direction:
+      - "25 GB mailbox."
+      - "$5 per inbox."
+      - "Domain email addresses."
+      - "DNS authentication setup."
+      - "Migration and device setup."
+      - "Local support."
+  - id: benefits_map
+    purpose: >
+      Translate technical features into buyer outcomes.
+    content_direction:
+      - "SPF/DKIM/DMARC -> better authentication and lower spoofing/spam risk."
+      - "S3 inbound buffering -> continuity during maintenance or server issues."
+      - "Amazon SES outbound -> deliverability tooling and sender-authentication foundation."
+      - "Hot standby -> reduced downtime risk."
+      - "Local setup/support -> fewer self-service admin failures."
+  - id: how_it_works
+    purpose: >
+      Explain the architecture without making unsupported guarantees.
+    content_direction:
+      - "1. We verify your domain and DNS."
+      - "2. We create mailboxes, aliases, forwards, and spam rules."
+      - "3. We migrate existing mail and configure Outlook/iPhone/iPad."
+      - "4. We monitor and support day-to-day changes."
+      - "Optional visual: inbound email -> S3 buffer -> mailbox delivery; outbound email -> SES -> recipients."
+  - id: pricing
+    purpose: >
+      Present the offer as simple and transparent while leaving room for migration/setup fees.
+    content_direction:
+      - "Single anchor: $5 per inbox/month, 25 GB included."
+      - "Separate setup/migration/support line items if they are not included."
+      - "Use a comparison row against Google Workspace Starter and Microsoft 365 Business Basic only for fit, not as attack copy."
+    decision_points:
+      - Clarify whether $5 includes support, DNS setup, migration, backup/buffering, and device setup or whether those are onboarding/support add-ons.
+      - Clarify billing interval, minimum mailbox count, cancellation policy, and whether taxes/fees apply.
+  - id: comparison
+    purpose: >
+      Differentiate against Google Workspace, Microsoft 365, and shared hosting.
+    content_direction:
+      - "Google Workspace: best when a business wants the full Google productivity suite and AI/collaboration bundle."
+      - "Microsoft 365: best when a business wants Microsoft apps, Teams, OneDrive, and broader Office ecosystem."
+      - "Shared hosting email: often cheap, but weaker support, deliverability, admin control, and resilience story."
+      - "Bay Area Email Services: best when a small local business wants professional email, careful DNS/migration, resilient hosting, and local support without buying a full office suite."
+  - id: trust_security
+    purpose: >
+      Reduce perceived risk around email infrastructure.
+    content_direction:
+      - "30+ years IT experience."
+      - "30+ local businesses supported, if verifiable."
+      - "Plain-English DNS/security explanations."
+      - "Corpus Christi / Coastal Bend local support."
+      - "Use exact terms: SPF, DKIM, DMARC, spam filtering, authentication, failover, S3 buffering, SES."
+    decision_points:
+      - Avoid absolute claims like 'no emails lost' or 'guaranteed inbox placement' unless backed by SLA/logging/legal review.
+      - Decide whether to publish uptime history, SLA, data retention, backup, and incident-response language.
+  - id: migration_onboarding
+    purpose: >
+      Turn switching anxiety into a managed process.
+    content_direction:
+      - "What we need: domain access, user list, current provider details."
+      - "What happens next: discovery, DNS plan, mailbox creation, migration window, device setup, post-migration check."
+      - "Address downtime explicitly with realistic expectations."
+  - id: local_seo
+    purpose: >
+      Capture Corpus Christi and Coastal Bend demand while preserving product-led readability.
+    content_direction:
+      - "Primary URL idea: /business-email-hosting-corpus-christi or /business-email-services-corpus-christi."
+      - "Support pages/blogs: business email vs Google Workspace vs Microsoft 365; why business emails go to spam; SPF DKIM DMARC setup; email migration checklist; shared hosting email problems."
+      - "Use LocalBusiness/ProfessionalService structured data for the local company page and Product/Offer-style schema only where pricing/offer details are accurate."
+  - id: faq
+    purpose: >
+      Answer purchase-blocking questions and support SEO long-tail queries.
+    content_direction:
+      - "Is this Google Workspace or Microsoft 365?"
+      - "Can you migrate from Gmail/Yahoo/shared hosting?"
+      - "Will my emails stop going to spam?"
+      - "What does $5 per inbox include?"
+      - "Do you set up Outlook/iPhone/iPad?"
+      - "What happens if the mail server is down?"
+      - "Do you support aliases, forwards, shared inboxes, and auto-replies?"
+constraints:
+  - Keep claims legally and technically defensible; use 'designed to', 'helps', 'reduces risk', and 'supports' where infrastructure docs do not prove end-to-end guarantees.
+  - The page must work both as a local service landing page now and as a SaaS/product landing page later.
+  - Do not position directly against Google Workspace/Microsoft 365 as universally better; position by fit and buyer need.
+  - Existing content has encoding artifacts in src/pages/ServicesPage.tsx, so future implementation should normalize copy/encoding before reuse.
+assumptions:
+  - The product brand remains Bay Area Email Services unless a new SaaS brand/domain is chosen.
+  - The first target audience is small businesses in Corpus Christi/Coastal Bend, not national self-serve SaaS buyers.
+  - $5 per inbox is an ongoing mailbox price, while setup/migration/support terms still need clarification.
+  - The AWS/S3/SES architecture is already implemented or will be implemented as described in current materials.
+open_questions:
+  - Is there a separate setup fee, migration fee, monthly support plan, or minimum mailbox count?
+  - What exact uptime/failover/SLA claims are allowed?
+  - What retention period applies to S3-buffered inbound messages?
+  - Are testimonials, case studies, Google reviews, or named customer logos available?
+  - Will the site use the existing Bay Area IT domain, a subdomain, or a standalone product domain?
+  - Should the product target only Corpus Christi/Coastal Bend or expand to broader US small businesses?
+requested_output:
+  - A landingpage plan that converts the recommended_sections into wireframe-level content blocks.
+  - A pricing/packaging decision sheet clarifying what $5 includes and which services are add-ons.
+  - A claim-safety checklist for all infrastructure, deliverability, uptime, security, and migration claims.
+done_definition:
+  - The next role can draft a landingpage without rediscovering product facts, competitor anchors, SEO direction, or unresolved decisions.
+  - Each major section has a clear purpose, content direction, and known decision points.
+  - Unsupported claims are flagged before implementation.
+verification:
+  - Checked local project for existing email-service copy and product facts.
+  - Confirmed separate marketing folder exists and added this research handover under research/.
+  - Checked current public pages/docs for Google Workspace, Microsoft 365, Google Search Central, AWS SES, and AWS S3.
+  - Agent launch was attempted but blocked by the current collab thread limit; research was completed sequentially as fallback.
+sources:
+  - "Existing brief: C:/Users/a931627/Documents/gitea/bayarea/E-Mail Webseite Marketing/PROJECT_BRIEF.md"
+  - "Existing repo content: C:/Users/a931627/Documents/gitea/bayarea/byarea/src/data/seoData.ts"
+  - "Existing repo content: C:/Users/a931627/Documents/gitea/bayarea/byarea/src/pages/ServicesPage.tsx"
+  - "Google Workspace Business pricing/features: https://workspace.google.com/intl/en_US/business/"
+  - "Microsoft 365 Business Basic pricing/features: https://www.microsoft.com/en-us/microsoft-365/business/microsoft-365-business-basic"
+  - "Google SEO Starter Guide: https://developers.google.com/search/docs/fundamentals/seo-starter-guide"
+  - "Google LocalBusiness structured data: https://developers.google.com/search/docs/appearance/structured-data/local-business"
+  - "Amazon SES documentation overview: https://aws.amazon.com/documentation-overview/ses/"
+  - "Amazon S3 data durability documentation: https://docs.aws.amazon.com/AmazonS3/latest/userguide/DataDurability.html"

research/seo-local-research-handover.yaml

@@ -0,0 +1,215 @@
+goal: >
+  Informationssammlung fuer SEO und Local SEO einer separaten Marketing-Webseite/Landingpage
+  fuer Business Email Services in Corpus Christi und Coastal Bend.
+current_phase: >
+  research
+owner: >
+  swarm-researcher
+context:
+  - Das Angebot kombiniert lokale Einrichtung und Support mit gehosteter Business-E-Mail:
+    Domain-Adressen, Outlook/iPhone/iPad Setup, SPF/DKIM/DMARC, Migration, Amazon SES
+    Deliverability, AWS-Redundanz, 25 GB Mailboxen fuer $5 pro Inbox.
+  - Google Local Ranking wird offiziell stark durch Relevance, Distance und Prominence
+    beeinflusst; Google Business Profile, vollstaendige Services, Bewertungen und lokale
+    Signale sind deshalb fuer diese Seite relevant.
+  - Google empfiehlt eindeutige, beschreibende Title-Tags, hilfreiche Inhalte fuer echte
+    Nutzer und strukturierte Daten dort, wo sie den Seiteninhalt korrekt beschreiben.
+  - FAQ Rich Results sind fuer die meisten nicht-behoerdlichen und nicht-gesundheitsbezogenen
+    Websites stark eingeschraenkt; FAQ-Inhalte bleiben trotzdem sinnvoll fuer Nutzer,
+    interne Struktur und AI/maschinenlesbares Verstaendnis.
+  - Lokale Wettbewerber in Corpus Christi/Coastal Bend positionieren sich meist breit
+    als Managed-IT-, Cybersecurity-, VoIP-, Netzwerk- oder Cloud-Anbieter statt mit einer
+    dedizierten Business-Email-Hosting-Landingpage.
+  - Beispiele fuer lokale Wettbewerber/Referenzen: Coltarus Halo, 1820 Services, Southern
+    Sky Technologies, ReNetworked, Corpus Christi IT Services, Copano IT, ITECH2 und
+    Tech-Net. Viele sprechen IT-Support breit an; klare Email-only-Positionierung und
+    transparente Inbox-Preise sind weniger sichtbar.
+  - AWS SES kann eingehende E-Mails per Receipt Rules unter anderem in Amazon S3 speichern;
+    Amazon SES Virtual Deliverability Manager adressiert Inbox Deliverability, Reputation
+    und Authentifizierungsprobleme wie fehlende SPF/DMARC/DKIM-Eintraege.
+constraints:
+  - Separate Marketing-/SaaS-artige Seite soll eine Ebene ueber dem bestehenden Projekt
+    liegen: C:\Users\a931627\Documents\gitea\bayarea\E-Mail Webseite Marketing.
+  - Nicht ueberclaimen: Amazon SES, SPF, DKIM und DMARC als bessere technische Grundlage,
+    geringeres Spam-Risiko und staerkere Reputation formulieren, nicht als garantierte
+    Inbox-Platzierung.
+  - Corpus Christi sollte primaerer lokaler Fokus sein; Coastal Bend und Orte wie
+    Portland, Rockport, Aransas Pass und Kingsville sollten sekundaer und nicht als
+    duplizierte Doorway-Pages behandelt werden.
+  - Preisangabe "$5 pro Inbox" nur mit Abrechnungszeitraum und Leistungsumfang verwenden,
+    sobald das bestaetigt ist.
+assumptions:
+  - Zielkunden sind kleine Unternehmen, Office Manager, lokale Dienstleister und Teams,
+    die von Gmail/Yahoo, Webhost-Mail oder schlecht betreutem Microsoft/Outlook-Setup
+    weg wollen.
+  - Lokale Naehe, schneller Support und technische E-Mail-Kompetenz sind staerkere
+    Differenzierer als ein generisches "Managed IT" Versprechen.
+  - Die Seite darf sichtbare Preise, lokale Trust Proofs und eine direkte Assessment-CTA
+    verwenden.
+  - Es gibt oder soll ein Google Business Profile geben, dessen Services und Bewertungen
+    auf diese E-Mail-Leistung ausgerichtet werden koennen.
+open_questions:
+  - Soll die Marke "Bay Area Email Services", "Bay Area Business Email" oder ein neuer
+    SaaS-artiger Produktname werden?
+  - Ist "$5 pro Inbox" monatlich, jaehrlich, promotional oder an Mindestanzahl/Setup-Fee
+    gebunden?
+  - Sind Kalender/Kontakte/Groupware enthalten, oder ist das Produkt primaer IMAP/SMTP
+    Mailbox plus Outlook/mobile Einrichtung?
+  - Welche SLA-, Uptime-, Backup-, Retention- und Failover-Aussagen sind technisch und
+    rechtlich sicher belegbar?
+  - Soll die Seite nur lokal verkaufen oder spaeter national skalierbar als SaaS-Landingpage
+    funktionieren?
+requested_output:
+  - Landingpage-Plan mit einer kanonischen Hauptseite fuer Corpus Christi plus spaeteren
+    Support-/Vergleichsseiten fuer Migration, SPF/DKIM/DMARC und Outlook/iPhone Setup.
+  - SEO-Brief fuer Copy, Informationsarchitektur, FAQ, Schema und Google Business Profile.
+done_definition:
+  - Die naechste Rolle kann daraus direkt Seitenstruktur, Copy oder Frontend-Prototyp
+    erstellen, ohne die SEO-Grundlagen erneut zu recherchieren.
+  - Die Seite adressiert lokale transaktionale Suchintention, erklaert das Produkt klar,
+    differenziert sich gegen generische Managed-IT-Seiten und erzeugt Assessment- oder
+    Quote-Anfragen.
+keyword_clusters:
+  primary_local_transactional:
+    - business email services Corpus Christi
+    - business email hosting Corpus Christi
+    - professional business email Corpus Christi
+    - small business email setup Corpus Christi
+    - business email provider Corpus Christi
+    - custom domain email Corpus Christi
+  coastal_bend_modifiers:
+    - business email Coastal Bend
+    - business email hosting Coastal Bend
+    - IT support email setup Coastal Bend
+    - business email Portland TX
+    - business email Rockport TX
+    - business email Aransas Pass TX
+    - business email Kingsville TX
+  setup_support_intent:
+    - Outlook email setup Corpus Christi
+    - Outlook setup for business email
+    - iPhone business email setup
+    - iPad email setup for business
+    - email migration services Corpus Christi
+    - migrate business email from Gmail
+    - migrate business email from Yahoo
+    - move from web hosting email
+  deliverability_security_intent:
+    - SPF DKIM DMARC setup Corpus Christi
+    - why business emails go to spam
+    - email DNS setup for business
+    - DMARC setup for small business
+    - business email deliverability help
+    - domain email authentication setup
+  comparison_intent:
+    - Gmail vs business email
+    - web hosting email vs business email hosting
+    - Microsoft 365 vs local email hosting
+    - best email hosting for small business Corpus Christi
+    - affordable business email hosting
+  pricing_intent:
+    - $5 business email inbox
+    - affordable business email Corpus Christi
+    - 25 GB business email mailbox
+    - low cost business email hosting
+recommended_page_structure:
+  - Hero: "Business Email Hosting in Corpus Christi" mit Preis, 25 GB Mailbox, lokalem
+    Support und primaerer CTA.
+  - Problem: kostenlose Gmail/Yahoo-Adressen, Webhost-Mail-Ausfaelle, Spam-Folder,
+    verpasste Leads und Vertrauensverlust.
+  - Product: Domain-Mailboxen, info@/contact@/user@, Outlook, iPhone, iPad, Aliases,
+    Forwards, Auto-Replies und Custom Spam Filtering.
+  - Deliverability: SPF, DKIM, DMARC, DNS-Konfiguration, Amazon SES, Reputation und
+    plain-English Erklaerung.
+  - Reliability: AWS-Redundanz, S3-Inbound-Buffering, Hot Standby/Failover und
+    Wartungs-/Ausfallpositionierung nur soweit belegbar.
+  - Migration: Wechsel von Gmail, Yahoo, Webhost-Mail oder altem Provider mit minimaler
+    Unterbrechung.
+  - Local Support: Corpus Christi/Coastal Bend, lokale Telefonnummer, Onboarding,
+    Passwort-Resets, neue Nutzer, laufende Hilfe.
+  - Pricing: klarer per-inbox Preis, was enthalten ist, was optional/extra ist.
+  - FAQ: echte Kauf- und Setup-Fragen statt Keyword-Stuffing.
+  - CTA: "Book a 20-minute email setup assessment" und "Get a mailbox count quote".
+title_meta_ideas:
+  - title: "Business Email Services Corpus Christi | $5/Inbox Local Support"
+    meta: "Professional domain email hosting for Corpus Christi businesses. 25 GB mailboxes, Outlook and iPhone setup, SPF/DKIM/DMARC, migration, and local support."
+  - title: "Business Email Hosting in Corpus Christi | Bay Area Email Services"
+    meta: "Affordable business email hosting with 25 GB mailboxes, Amazon SES deliverability, AWS redundancy, DNS setup, migration, and Coastal Bend IT support."
+  - title: "Professional Email Setup Corpus Christi | Outlook, SPF, DKIM, DMARC"
+    meta: "Upgrade from Gmail, Yahoo, or web-host email. We set up domain email, Outlook, iPhone, iPad, DNS records, spam protection, and email migration."
+faq_targets:
+  - question: "What is a professional business email address?"
+    intent: "Domain-based email versus free Gmail/Yahoo erklaeren."
+  - question: "Why are my business emails going to spam?"
+    intent: "SPF/DKIM/DMARC und DNS-Fehlkonfiguration verstaendlich erklaeren."
+  - question: "Can you migrate my old email?"
+    intent: "Migration von Gmail/Yahoo/Webhost/Altanbieter abfangen."
+  - question: "Does this work with Outlook, iPhone, and iPad?"
+    intent: "Client- und Device-Setup-Bedenken beantworten."
+  - question: "How much does business email cost?"
+    intent: "$5/inbox und 25 GB Mailbox transparent machen."
+  - question: "Is this Microsoft 365?"
+    intent: "Positionierung gegenueber Microsoft 365 klaeren, ohne Kaeufer zu verwirren."
+  - question: "Do you support businesses outside Corpus Christi?"
+    intent: "Coastal-Bend-Servicegebiet natuerlich einbinden."
+  - question: "What do SPF, DKIM, and DMARC do?"
+    intent: "Technische Autoritaet und Vertrauen aufbauen."
+content_gap_opportunities:
+  - Dedizierte Email-only-Landingpage statt Email als Unterpunkt in Managed IT.
+  - Sichtbarer per-inbox Preis; viele lokale IT-Anbieter erzwingen erst Kontaktaufnahme.
+  - Plain-English-Seite zu SPF/DKIM/DMARC mit Bezug auf verpasste Leads und Spam-Folder.
+  - Vergleichscontent: Gmail/Yahoo vs Domain Email, Webhost Email vs Managed Business
+    Email, Microsoft 365 vs lokal betreutes Email Hosting.
+  - Lokaler Proof: 30+ Jahre IT-Erfahrung, 30+ lokale Unternehmen, konkrete Orte,
+    Branchen, Testimonials, Response-Zeiten.
+  - Technischer Trust ohne Ueberladung: SES, AWS-Redundanz, S3-Buffering, Failover und
+    25 GB Mailboxes als Business-Vorteile statt Infrastruktur-Deep-Dive.
+  - Setup-Workflow: Domain-Zugang, Mailboxliste, Migrationsfenster, Device Setup,
+    DNS-Verifikation, Go-live-Checkliste.
+concrete_seo_recommendations:
+  - Eine kanonische Landing-URL nutzen, z.B. /business-email-corpus-christi/ oder
+    /email-services-corpus-christi/.
+  - H1 mit Service und Ort: "Business Email Hosting in Corpus Christi".
+  - Above the fold: Preis, Mailboxgroesse, lokale Hilfe und Domain-Email-Versprechen
+    sichtbar machen.
+  - LocalBusiness oder ProfessionalService Schema mit Name, URL, Telefon, Service Area,
+    Adresse/Area Served, Opening Hours, sameAs und angebotenen Services verwenden.
+  - Service Schema fuer Business Email Services/Email Hosting ergaenzen, wenn die Seite
+    den Service klar beschreibt.
+  - FAQPage Schema nur als semantische Hilfe einbauen; nicht als Traffic-Hebel fuer
+    Google FAQ-Dropdowns verkaufen.
+  - GBP Services abstimmen: Business Email Services, Email Hosting, Email Migration,
+    Microsoft Outlook Setup, IT Support, SPF/DKIM/DMARC Setup.
+  - Kundenbewertungen gezielt, aber natuerlich einsammeln; Wuensche: "business email",
+    "Outlook setup", "email migration", "Corpus Christi", "local support".
+  - Keine duplizierten Ortseiten fuer jede Stadt erstellen, solange kein einzigartiger
+    lokaler Inhalt/Proof vorhanden ist; lieber ein starkes Service-Area-Modul.
+  - Spaetere Content-Seiten priorisieren: "Why business emails go to spam", "SPF DKIM
+    DMARC setup for small businesses", "Business email migration checklist", "Outlook
+    and iPhone business email setup".
+verification:
+  - Swarm-research Skill und Handover-Contract gelesen.
+  - Vorhandener Zielordner geprueft: C:\Users\a931627\Documents\gitea\bayarea\E-Mail Webseite Marketing.
+  - Ein Subagent fuer Keyword/Local-Intent-Research wurde erfolgreich gestartet und
+    ausgewertet; weitere Agent-Spawns waren durch Thread-Limit blockiert.
+  - Web-Recherche mit aktuellen Quellen zu Google Local SEO, Google Title/Content/FAQ
+    Guidance, AWS SES, Amazon S3 Receiving und lokalen Corpus-Christi-Wettbewerbern
+    durchgefuehrt.
+  - Handover-Datei wurde erstellt.
+sources:
+  - "Google Business Profile local ranking: https://support.google.com/business/answer/7091/improve-your-local-ranking-on-google"
+  - "Google LocalBusiness structured data: https://developers.google.com/search/docs/appearance/structured-data/local-business"
+  - "Google title link guidance: https://developers.google.com/search/docs/appearance/title-link"
+  - "Google helpful content guidance: https://developers.google.com/search/docs/fundamentals/creating-helpful-content"
+  - "Google FAQ/HowTo rich result changes: https://developers.google.com/search/blog/2023/08/howto-faq-changes"
+  - "Amazon SES S3 receiving action: https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-s3.html"
+  - "Amazon SES Virtual Deliverability Manager: https://docs.aws.amazon.com/ses/latest/dg/vdm.html"
+  - "Amazon SES email receiving: https://docs.aws.amazon.com/ses/latest/dg/receiving-email.html"
+  - "Coltarus Halo competitor reference: https://www.coltarushalo.com/"
+  - "1820 Services competitor reference: https://1820services.com/"
+  - "Southern Sky Technologies competitor reference: https://getsouthern.com/"
+  - "ReNetworked competitor reference: https://www.renetworked.com/"
+  - "Corpus Christi IT Services competitor reference: https://ccitservices.net/"
+  - "Copano IT competitor reference: https://www.copanoit.com/contact/"
+  - "ITECH2 Corpus Christi competitor reference: https://itech2.net/city/corpus-christi/"
+  - "Tech-Net competitor reference: https://www.tech-net.com/"