WP Job Manager Job Alerts registers a job_alert custom post type for every saved search a logged-in user creates. Each alert stores search_keywords, search_location, search_categories, search_job_types and an alert_frequency (daily, weekly, fortnightly) in postmeta. The admin lets you list them per user. It does not let you see what your candidates are collectively waiting for.

SleekView reads wp_posts rows where post_type = 'job_alert', joined to wp_postmeta for the search criteria, plus the linked job_listing_category and job_listing_type taxonomies referenced by the alert. Group by search_keywords for top demanded queries, by search_location for geographic intent, by search_categories for category demand, or by alert_frequency to see how patient your audience is.

A regional board with 4,100 active alerts found that 22 percent of all alerts referenced the same three keyword phrases. Those phrases had thin job inventory. Within a month they had reached out to two specific employer types to fill that gap. The data was always in the job_alert CPT. They had just never looked at it in aggregate.

Alerts are the highest-intent signal on a job board. A candidate has logged in, expressed a precise search, and opted in to ongoing emails. WP Job Manager Job Alerts captures all of that in the job_alert custom post type and its postmeta but offers no aggregate view, so most operators never look at the data they spent acquisition dollars to collect.

SleekView Charts turns those rows into a true demand-side dashboard: which keywords candidates are actively waiting for, which locations have unmet demand, how frequency mix shifts as your audience matures, and how alert creation velocity responds to your marketing. That intelligence reshapes every important decision on a job board, from employer outreach to editorial calendar to email cadence. Alerts already exist in your database.

SleekView Charts simply makes them visible at the scale they matter at.