LKG Training Pack

Start here

Use these owned routes first when you want the clearest path into guides, next steps, and local markets.

TRAINING PAGE

Training page

Sandbox only. Not a production page.

Buyout coverage

Advertising & Provider Info

We do not sell shared ad placements. We sell ownership of the decision layer.

Overview

When no buyout is active, the page-level CTA flow and lead form belong to the platform. When a buyout is active, those same runtime surfaces become sponsor-owned for the covered page.

Runtime CTAs are the source of truth. We do not force a fixed CTA count across all page types.

Sales page contract

This page is the authoritative public buyout and routing document. It is not a live sponsor surface.

Sponsorship Options

Pricing varies based on market size, competition, and existing sponsor coverage.

City Buyout

Starting at $2,500/month

Own all high-intent demand for a single city.

  • Sponsor-owned CTAs on that city page
  • All leads routed directly to your firm
  • Control of the primary decision points
Check availability

State Buyout

Starting at $7,500/month

Own demand across an entire state.

  • Sponsor-owned CTAs across the state page
  • Exclusive lead routing
  • Coverage across key decision surfaces
Check availability

Vertical Buyout

Starting at $25,000/month

Own the entire category across guides, states, and select cities.

  • Homepage
  • All guide pages
  • Up to 10 cities
  • Corresponding states
  • Additional cities available
Check availability

Products

City Buyout

  • Owns sponsor-visible CTA routing on that city page
  • Owns sponsor lead flow on that city page
  • If a directory exists, the CTA above the directory becomes the sponsor feature surface
Sponsorship inquiry

State Buyout

  • Owns sponsor-visible CTA routing on that state page
  • Owns sponsor lead flow on that state page
  • If a directory exists, the CTA above the directory becomes the sponsor feature surface
Sponsorship inquiry

Vertical Buyout

  • Includes homepage / vertical hub coverage
  • Includes all guide pages
  • Includes up to 10 cities by default, plus corresponding states
  • Additional cities are available as a paid expansion
  • Personal Injury excludes city pages because those pages are not rendered
Sponsorship inquiry

How sponsor ownership works

Visual explanation

Clean page vs owned page
Side-by-side example of a clean page with platform-owned CTAs and an owned page with sponsor-owned CTAs.
Clean pages keep the platform CTA flow. Owned pages switch the same runtime CTA surfaces into sponsor-owned decision points.
Composite buyout coverage
Composite visual showing homepage, state page, guide page, and eligible city page coverage with sponsor-owned CTA surfaces highlighted.
Vertical buyout covers homepage, all guides, and the covered market pages in the contract. CTA ownership is highlighted because the CTA layer is the monetized decision surface.

Vertical buyout includes homepage, all guide pages, up to 10 cities by default, and the corresponding states. Existing active city or state contracts are not silently overridden.

Directory CTA feature
Directory page example where the CTA block above the directory becomes the sponsor feature surface while the directory listings remain visible and neutral.
The CTA directly above a directory becomes the sponsor feature surface under buyout. The directory stays visible for context and is not reordered to fake rankings.
Sponsor lead form example
Sponsor-owned lead flow example showing CTA click, sponsor-branded inquiry form, and exclusive lead delivery to the sponsor.
On a bought-out page the lead form follows the same sponsor-owned path as the CTA layer, and all captured leads route directly to the sponsor.

Lead routing note: All leads submitted through this sponsor flow go to the sponsor when buyout routing is active.

Start a sponsorship inquiry

Use the inquiry button below if you want a City Buyout, State Buyout, or Vertical Buyout.

Start inquiry
Related search pathsAdditional owned routes for this topic

These routes support fanout/query coverage and keep owned paths visible, but they are intentionally secondary to the main framework and next-step flow.