Google XML Sitemaps stores its configuration as a serialized array in wp_options under sm_options. Per-post inclusion flags and priority overrides live in wp_postmeta under keys like sm_priority and sm_exclude. The plugin reads both at sitemap generation time to decide what URL appears, at what priority, with which change frequency.

The default admin gives a settings screen for the global rules and a per-post checkbox for exclusions, but no single surface that shows what the next sitemap will actually contain. Editors who need to confirm that a launch post is included, or that thirty stub pages were excluded, have to click into each post individually.

SleekView reads wp_posts joined with the plugin's postmeta keys and the resolved option set, so every post's effective sitemap state shows in one grid. Inline edits to priority, change frequency, or exclusion write back through standard postmeta updates and the next sitemap rebuild reflects the change.

Google XML Sitemaps does its job well: it reads WordPress posts, applies inclusion rules, and emits valid XML. The problem is auditing what the next sitemap will contain. The plugin's UI exposes settings, not the resulting manifest, so editors have to trust the rules and discover surprises in Search Console after submission.

On a site with hundreds of posts and several custom post types, that trust is misplaced often enough to cost rankings. SleekView reads the same postmeta and option values the plugin reads, joins them into one grid, and shows the effective sitemap state per row. Filter for excluded posts, sort by priority, find every override that diverges from the global default.

The plugin still owns generation and rewrite rules. SleekView just makes the sitemap visible before it goes to Google, which is what the operational job actually requires.