A page consolidation is not complete when redirects go live. Search Console must show whether one preferred page gains query ownership without losing valuable long-tail coverage, clicks, conversions, or crawl signals. A 28-day comparison gives early direction while preserving a longer review window for slower changes.
Use this after merging overlapping blog posts, service pages, release guides, location pages, tag archives, or comparison pages into one canonical resource.
Quick answer
Search Console Consolidation 28 Day Before and After Report Template should be handled with a narrow evidence-first workflow: freeze baseline, build complete destination, update every signal, then verify the result before making broader changes.
What to check first
- Freeze the pre-change URL set, canonical tags, redirect plan, query-to-page pairs, clicks, impressions, CTR, position, conversions, and incoming internal links.
- Choose one destination that fully answers the combined intent, then preserve useful examples, media, tables, and sections from the retired pages.
- Implement direct server-side redirects, update canonical tags, sitemap entries, navigation, contextual links, structured data, and campaign destinations.
- Compare matched 28-day windows by query, page, country, device, and search appearance while annotating seasonality and Google updates.
- Review lost queries and wrong-page impressions weekly, then restore a distinct page only when its intent is genuinely different.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Freeze baseline | Freeze the pre-change URL set, canonical tags, redirect plan, query-to-page pairs, clicks, impressions, CTR, position, conversions, and incoming internal links. | Every retired URL redirects directly to the preferred canonical page and is absent from the sitemap. |
| Build complete destination | Choose one destination that fully answers the combined intent, then preserve useful examples, media, tables, and sections from the retired pages. | Internal links and structured data point to the preferred URL without chains or mixed canonicals. |
| Update every signal | Implement direct server-side redirects, update canonical tags, sitemap entries, navigation, contextual links, structured data, and campaign destinations. | The 28-day report shows query ownership, clicks, impressions, CTR, position, and conversions by page. |
| Compare matched windows | Compare matched 28-day windows by query, page, country, device, and search appearance while annotating seasonality and Google updates. | Any lost query is classified as normal volatility, snippet mismatch, missing section, or genuinely separate intent. |
Why this usually happens
- Several related pages can split impressions because internal links and titles do not establish one clear owner.
- A broad merge can remove the exact section that ranked for a valuable long-tail query.
- Redirect chains, stale canonicals, old sitemap URLs, and unchanged internal links slow signal consolidation.
- Average position can improve while clicks fall if the surviving title or answer no longer matches the query.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
consolidation_report:
preferred_url: /blog/avada-changelog-security-update-priority-board
retired_urls: 2
comparison_days: 28
dimensions: [query, page, country, device]
checks: [redirect, canonical, sitemap, internal_links, conversions]
decision_date: 2026-08-14
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Freeze baseline
- Build complete destination
- Update every signal
- Compare matched windows
- Review lost intent
What to tell the client or owner
Share the URL map, redirect and canonical evidence, sitemap state, before and after exports, top gained and lost queries, conversion comparison, annotations, and next review date.
Production verification checklist
- Every retired URL redirects directly to the preferred canonical page and is absent from the sitemap.
- Internal links and structured data point to the preferred URL without chains or mixed canonicals.
- The 28-day report shows query ownership, clicks, impressions, CTR, position, and conversions by page.
- Any lost query is classified as normal volatility, snippet mismatch, missing section, or genuinely separate intent.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, measure a WordPress content consolidation.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references