Skip to content
NPCLocal

Internal wiki

NPCLocal improvement plan

This page records the current revenue, SEO, and AEO cleanup pass. The working thesis is simple: NPCLocal already has serious marketplace infrastructure, so the next gains come from clearer packaging, safer claims, and source-of-truth discipline.

Operating diagnosis

NPCLocal should be treated as a local-services lead-routing business with an AEO data layer. The fastest revenue path is selling exclusive tracked routing slots to providers. SEO and AI-answer visibility are the compounding back-end, not the only monetization path.

Shipped in this pass

  • Refreshed README and project docs so NPCLocal is described as the live lead-routing marketplace, not the old weather/sponsor site.
  • Added this wiki page as the durable record for the current commercial and SEO/AEO cleanup pass.
  • Promoted the pro acquisition path in primary navigation.
  • Softened sales and schema copy so claims stay scoped to NPCLocal-routed calls/forms and not all market demand.
  • Documented source-of-truth drift as an operational risk to fix before scaling content production.

Money-now improvements

Sell the routing slot, not the portal

The simplest paid offer is one provider owning a category/city or coverage-area routing slot. The pitch should lead with tracked local calls/forms, recordings, audit emails, and monthly reporting.

Use real demand counts

Public claim checkout already gates on recent click-intent demand. Use those counts in outbound and slot-status pages instead of broad SEO promises.

Make the pro path obvious

Customers can still search first, but the site needs a visible owner path: List your business, own a trade, and claim a proven slot.

Reduce breadth until revenue sharpens

Jobs, hire board, prices, estimates, Ask, Daily, and guides are useful, but they should support the service-routing marketplace instead of competing with it as separate products.

SEO and AEO priorities

  • Keep page HTML, JSON feeds, OpenAPI, sitemap, and llms.txt in sync.
  • Add first-party review collection and provider proof before claiming stronger trust signals.
  • Prioritize high-value, locally specific category pages over raw page-count expansion.
  • Build proof pages: sample monthly report, how call routing works, open slots with demand, and what each paid plan includes.
  • Resolve NAS/GitHub/VPS source drift before publishing another large content wave.

Source-of-truth warning

Before scaling content or deploying strategic edits, verify NAS, GitHub origin, and VPS are on the same commit. Live sitemap/content drift weakens both search trust and AI-agent trust because those systems can compare HTML, feeds, sitemaps, and agent guides.