1. Home
  2. Local Content Engine
  3. How to Setup Local Content Engine
Searching...

How to Setup Local Content Engine

Contents

This guide covers the base setup for Local Content Engine inside LaunchSMS.

What You Need

Before you begin, make sure you have:

  • A Launch365 account with access to Integrations
  • At least one supported provider connected or planned
  • Brand assets ready for optional AI image/video generation
  • A destination for the content, such as Launch365 AI Websites, WordPress, GBP, or YouTube

Step 1: Open the Integration

  1. Log into Launch365
  2. Go to Settings > Integrations
  3. Open Local Content Engine

Step 2: Enable the Module

Under Module Controls, turn on:

  • Enable Local Content Engine

Optional but recommended:

  • Use Queue Processing

Queue processing is recommended because it improves reliability and keeps generation work out of the request cycle.

Step 3: Choose Your Content Providers

Under Enabled Providers, turn on the platforms that are allowed to create mini jobs.

Available provider toggles include:

  • ServiceTitan
  • Housecall Pro
  • Jobber
  • Dispatch Scout
  • FieldPulse

Only enabled providers can generate Local Content Engine events.

Step 4: Configure Brand Assets

Under Brand Assets + Recap Defaults, upload or review:

  • Primary Logo Attachment
  • Secondary Reference Attachment

These assets are used to guide AI-generated media and branded video recap output.

Step 5: Configure AI Media Options

If you want media generated automatically, turn on the options you need:

  • Enable AI Image Creation (Nano Banana)
  • Enable AI Video Creation (VEO)

Then choose recap defaults such as:

  • Aspect ratio
  • Duration
  • Resolution

Video duration can be configured up to 12 seconds.

Step 6: Configure WordPress or Automation Settings

Optional settings include:

  • WordPress Sync Webhook URL for WordPress page sync
  • Enable Mini-Post Automation Trigger for GBP Syndication if you want mini-job creation to trigger automations

Use this if you want content to automatically flow into:

  • Google Business Profile
  • YouTube
  • WordPress page sync

Step 7: Configure Where the Content Displays

Local Content Engine controls ingest and generation. Display configuration happens elsewhere.

Choose one or both of these:

Launch365 AI Websites

Use AI Website Builder to control:

  • Service-area page layout
  • URL structure
  • Global map behavior
  • Service-type pinning

WordPress websites

Use the Launch365 WordPress plugin and the 

 shortcode to display:

  • City pages
  • Service pages
  • Mini-job cards
  • Maps
  • Pagination

Step 8: Test with a Completed Job Event

Once setup is complete, run a test completed-job event from one of your enabled providers.

Then confirm:

  • A mini job was created
  • AI content generated correctly
  • Images generated if enabled
  • Video generated if enabled
  • Content appeared in the intended website destination
  • Automations fired if configured

For the cleanest first test:

  1. Enable one provider only
  2. Use queue processing
  3. Turn on AI image generation first
  4. Turn on AI video generation after confirming the content flow works
  5. Check the mini job inside Local Content Engine > Mini Job Management

Troubleshooting Checklist

If Local Content Engine is not producing content, check:

  • The integration is enabled
  • The provider toggle is enabled
  • The provider itself is connected
  • Queue workers are running if queue mode is on
  • AI media toggles are enabled only if you intend to generate media
  • WordPress webhook URL is valid if using WordPress sync
  • Automations are active if expecting GBP or YouTube publishing

Next Guides

Updated on March 26, 2026
Tagged:
Was this article helpful?
Yes No

Related Articles

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.