[appdevelopsk]

Why

The newly-added catalog's purpose filters contained obsolete aliases flinch (the published catalog slug is daily-duel) and pickwhirl (published slug chore-roulette). The source had no automated filter-to-published-catalog validation, so future renames or delistings could create silently empty category views. Acquisition content only covered two of the four browsing intents.

Implementation

• Correct invalid purpose-filter aliases while preserving the published 92-app cards, organic crawlability and all Play Install Referrer links.
• Add two unique, intent-led editorial landing pages /guides/decision-helpers/ and /guides/ai-tools/: four verified-visible catalog apps each, practical selection advice, transparent first-party publisher disclosure, truthful ItemList data, canonical and OG metadata, direct Play attribution and anonymous GA4 store-click events.
• Internal links from homepage, /apps and between guide pages, add sitemap entries.
• Expand existing dry-run-by-default non-deleting VPS release script and read-only live check to include both pages. No VPS or store deployment performed here.
• CI rejects stale/hidden category slug references, checks every 4-app guide against catalog, and derives current visible count from site_counts.json rather than freezing at 92.

Outcome measurement

After operator publishes the site and live check passes, compare Google organic guide landing sessions, discovery_nav_click, catalog_filter_used, guide_store_click, Google Play visitors/acquisitions, and first completed in-app action. No claim of increased user count until live data.