Cleveland by Jay

Author: Jay

  • Untitled post 9765
  • Safety outlet installed

    Safety outlet installed

  • How to add a new POC for all web security notifications

    How to add a new POC for all web security notifications

     

    🔐 STEP 1 — Create One Security Email (10 Minutes)

    Instead of adding Ricardo everywhere manually, create:

    security@studiohaus.site
    (or security@catalystwin.com — whichever is primary)

    Then:

    • Add Ricardo to that inbox (or forward all emails to him)
    • Keep existing recipients exactly as they are
    • Use this email only for security/system alerts

    This becomes the single point you plug into everything.

    🔐 STEP 2 — InMotion Hosting (Main Provider)

    A. Add Ricardo as a cPanel User (Fastest Clean Method)

    1. Log into InMotion AMP
    2. Go to Account Management → cPanel
    3. Add a new cPanel user (if allowed on your plan)
      OR
    4. Add his email under:
      • Contact Information → Email → “Contact Email”
      • Check “Receive notifications”

    Make sure the following are enabled:

    • Security advisories
    • Account suspension warnings
    • Resource usage alerts

    If cPanel doesn’t allow multiple contacts, forward all server alerts to:
    security@studiohaus.site

    🔐 STEP 3 — WordPress (Very Important)

    Do this on each site.

    If Using Wordfence:

    1. WP Admin → Wordfence → All Options
    2. Scroll to Alert Preferences
    3. Add:
      security@studiohaus.site

    Enable:

    • Critical problems
    • Administrator login alerts
    • Plugin vulnerability alerts

    If Using No Security Plugin (Important)

    Install:

    • Wordfence (free is fine for now)

    Turn on:

    • Email alerts for critical issues only

    🔐 STEP 4 — Cloudflare (If Used)

    1. Log in
    2. Go to Profile → Notifications
    3. Add security@studiohaus.site

    Enable:

    • DDoS alerts
    • DNS changes
    • SSL changes
    • Firewall events

    If you don’t know whether Cloudflare is being used:

    • Check nameservers in domain registrar

    🔐 STEP 5 — Domain Registrar

    Wherever domain is registered:

    1. Add security@studiohaus.site as:
      • Technical contact
      • Admin contact (optional)

    Enable:

    • Expiration alerts
    • DNS changes
    • WHOIS updates

    🔐 STEP 6 — Stripe / Payment Gateways

    Stripe:

    1. Settings → Team
    2. Add Ricardo as:
      • Analyst (view only)
        OR
    3. Add security@studiohaus.site under:
      • Email notifications → Fraud alerts

    Enable:

    • High-risk payments
    • Login from new device
    • Account changes

    🔐 STEP 7 — For studiohaus.site (Unknown Hosting)

    Fastest way to identify host:

    1. Go to:
      https://who.is
    2. Enter studiohaus.site
    3. Check:
      • Nameservers
      • Hosting provider
      • Registrar

    Then repeat Steps 2–6 for that provider.

    🚨 Absolute Minimum (If You Want Ultra Fast)

    If you want the 80/20 solution in 30 minutes:

    1. Create security@studiohaus.site
    2. Add it to:
      • InMotion contact email
      • Wordfence alerts
      • Stripe fraud alerts
    3. Forward all mail from that inbox to Ricardo

    Done.

    That gives you redundancy immediately.

    This keeps:

    • Eric operational
    • Jay protected
    • Ricardo layered in
    • Zero restructuring
    • Maximum oversight

    No process disruption.

  • Gaining Additional Direct Bookings Requires Perfect Configuration

    Gaining Additional Direct Bookings Requires Perfect Configuration

    Gaining Additional Direct Bookings Requires Perfect Configuration

    Step #1: Distribution Must Be Correct Before Marketing Begins

    Before campaigns, ads, SEO, Google Vacations, or corporate outreach — configuration comes first.

    If the plumbing is wrong, traffic is wasted.

    STEP #1 — Directo Must Appear When Someone Searches on Booking.com

    Since your CRM is Hospitable, and Direct bookings are powered through it, configuration happens at three levels:

    Level 1: Hospitable → Direct Site Configuration

    Hospitable controls:

    • Direct booking pages
    • Property naming
    • Photos
    • Description
    • Tags
    • Sync behavior

    As shown in the Hospitable property detail example ,
    Hospitable receives details from Airbnb but allows manual overrides for Direct.

    That means:

    ✔ Public name must be optimized
    ✔ Summary must be conversion-focused
    ✔ Tags must be correctly set
    ✔ Photos reordered intentionally for Direct
    ✔ House rules aligned
    ✔ Rental agreement + verification properly disclosed

    If Hospitable is not clean, Direct will never convert properly.

    Level 2: OTA Naming + Structure (Airbnb & Booking.com)

    Your listings currently exist and are connected .

    If someone searches on Booking.com:

    • The listing title
    • The property type
    • The neighborhood signal
    • The amenities
    • The price structure

    must align with what Direct shows.

    Mismatch creates distrust and kills Direct conversion.

    The Airbnb guidance on listing clarity confirms:
    Descriptions must be brief, realistic, and lead with key features .

    If Booking.com shows one positioning
    and Direct shows another —
    Google and users downgrade trust.

    Level 3: Google Vacation / Google Travel Qualification

    To appear on Google Vacation rentals:

    You need:

    • Structured data (schema markup)
    • Direct booking engine crawlable
    • Clean property URLs
    • Stable pricing logic
    • No broken availability sync

    This ties directly to Hospitable configuration.

    If Hospitable sync is inconsistent:
    Google may show OTA only.
    Direct won’t qualify.

    What “Perfect Configuration” Means Operationally

    1. Inventory Clarity

    Your listings by property structure are clearly mapped .

    Parent-child relationship must be reflected consistently:

    • 2007Full
    • P2007R1
    • P2007S4
    • etc.

    If Google sees duplicates with unclear hierarchy, ranking weakens.

    2. Pricing Transparency

    Your corporate pricing strategy is clearly defined :

    • $50 Standard
    • $75 Suite
    • $150 2BR
    • $400 6BR

    If Direct shows flat-rate clarity
    but OTA fluctuates aggressively,
    you lose price authority.

    Direct must:

    • Clearly explain flat-rate logic
    • Show long-term savings
    • Maintain consistency in messaging

    3. Verification Disclosure (Critical)

    If you use Hospitable verification portals,
    you must disclose this in listing descriptions to comply with OTA policies .

    If not disclosed:
    Booking.com may block link sharing.
    Guests may flag your account.
    Directo pathway breaks.

    What Must Be True Before Moving Forward

    Step #1 checklist:

    □ All listings correctly synced in Hospitable
    □ Direct pages manually optimized (not Airbnb copy-paste)
    □ Naming consistent across OTA and Direct
    □ Pricing tier explanation aligned
    □ House rules unified and enforceable
    □ Verification disclosure added
    □ No duplicate parent/child confusion
    □ Booking.com allows Hospitable guest portal link

    Until that is perfect,
    “Gaining Additional Direct Bookings” is theory.

    Larger Strategic Reality

    Direct bookings are not marketing.

    They are:

    1. Configuration
    2. Authority alignment
    3. Structured data correctness
    4. Distribution symmetry
    5. Trust continuity across platforms

    Marketing only amplifies what already exists.

    If configuration is imperfect,
    marketing amplifies confusion.

    When you are ready, we move deeper into:

    • Booking.com link-sharing mechanics
    • Directo exposure strategy
    • Google Travel qualification audit
    • Schema validation
    • OTA → Direct conversion funnel mapping

    Step #1 is configuration discipline.

    Nothing else matters before that.