Blog Merger handles the rarely-glamorous job of folding multiple WordPress installs (or subsites in a multisite) into a single destination. It writes per-job state to wp_options under blog-merger-prefixed keys, and crucially keeps a mapping log linking source-blog post IDs to the merged-destination post IDs inserted into wp_posts. Author, category, and tag mappings get the same treatment so the destination blog ends up with a coherent provenance even though the source content came from heterogeneous sources.

The plugin's UI lists recent merge jobs with a basic pass or fail indicator. The mapping log lives in option rows that nobody opens by hand. When an editor on the merged site asks where a specific post originally lived, the answer is technically present but operationally invisible.

SleekView reads the merge-job log and mapping records as a workspace. Each job becomes a row with source-blog identifier, post counts by type, author count, and outcome. A second view exposes the per-post mappings (source-blog id, source-post id, destination-post id, source author handle) as a queryable join against wp_posts, so editorial provenance after a merge is a saved filter rather than a recovered memory.

Merging blogs is one of those operations everyone hopes to do once and forget about, which is exactly why the mapping log is the most valuable artefact a merge plugin produces. Three months after a merge an editor will ask where a specific article originally lived. Six months later an authorship admin will discover that two contributors had the same display name across source blogs and the merger silently picked one.

A year later a content audit will flag posts that came from a source blog whose editorial standards differed from the destination. Without a queryable mapping log, every one of those questions becomes archaeology. Reading the per-post mapping records as a workspace turns archaeology into a saved filter.

Editorial teams see provenance in a column. Authorship admins resolve conflicts from a cohort instead of a per-job log scroll. Content auditors filter merged posts by source blog for review.

Bulk operations on a specific merge job (status changes, term cleanup, attribute corrections) become a single filtered action rather than a per-post hunt. That is what makes blog merging an operation you can repeat with confidence rather than a one-shot you hope worked.