XML Sitemap Generator for Google reads configuration from wp_options under keys like xmlsg_general_settings and per-post overrides from wp_postmeta (typically _xmlsg_priority and _xmlsg_exclude). Each post type can declare its own inclusion default, and individual posts can override priority, change frequency, or exclusion.

The default admin shows the general settings on one screen and exposes per-post overrides through a meta box inside each post. There is no surface that shows what the next sitemap will actually contain across post types. Validating a launch sitemap or auditing exclusions on a multilingual or multi-CPT site becomes a click-through marathon.

SleekView reads the post table joined with the plugin's postmeta keys and resolved option set, then renders one grid where each row mirrors an entry the sitemap will emit. Inline edits to priority, frequency, or exclusion write back through standard postmeta and the next regeneration reflects the change.

XML Sitemap Generator for Google does what it promises: it reads post types, applies inclusion rules, and emits a valid sitemap. The problem is that auditing the resulting manifest is impossible from inside the plugin's admin. Settings screens show rules, not outputs.

So editors and SEO leads trust the rules and discover surprises in Search Console after the fact. On a site with hundreds of posts and several CPTs, those surprises happen often enough to matter. SleekView reads the same postmeta and option values the plugin reads, joins them into a single grid, and shows the effective sitemap state per row.

Priority, change frequency, exclusion, post type, and last modified all become sortable, filterable columns. The plugin still owns generation. SleekView makes the manifest visible before submission, which is what an SEO triage workflow actually needs.