Protect organic traffic after a redesign with a 301 redirect map
Finds old URLs that earned organic clicks, checks which now return 404 or 410, maps each to the best new page by topic and creates the 301s only after your approval, then verifies them.
When to use it
When you relaunched or redesigned your site and fear that old URLs now return 404 and you are losing organic traffic.
What you get
A redirect map of old URLs with clicks, top query, status and proposed 301 target, created only after your approval and then verified, plus a 3-line summary for management.
Does it change anything in my account?
Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.
Works with
Search Console
Fill in before sending
[relaunch date][domain]
We relaunched the site on the hosting server on [relaunch date] and I need to make sure no organic traffic was lost to broken URLs.
1. Find the matching Search Console property and the hosting server for [domain].
2. Pull Search Console data by page and query together, sorted by clicks. Search Console counts days back from today, so set the lookback to cover the 90 days before [relaunch date] plus the days since; tell me the exact window you used and note that it includes some post-relaunch clicks. If I paste a Search Console export for the exact pre-relaunch window, use that instead. From this, keep pages with at least 10 clicks and take the top query per page from the same data.
3. Request each of those URLs on the live site, highest clicks first, in batches, and record the HTTP status and any Location header.
4. List the current redirect rules and the current site files. For every URL returning 404 or 410, propose the closest matching new page by topic, not just by similar slug (read the candidate page outline if needed). If no good match exists, say so instead of sending it to the homepage.
Deliver a table: old URL, clicks (window), top query, current status, proposed 301 target, confidence (high/medium/low).
Sort by clicks. Flag any proposed rule that would create a chain or loop with the existing redirect rules. Show me the full map as a redirect preview and wait for my approval before creating any redirect.
After I approve, add the 301s (paths as source, keeping existing rules), re-request each old URL to confirm it returns a single 301 whose target returns 200, and inspect the 5 highest-click targets in Search Console to confirm they are indexed or indexable with the expected canonical. End with 3 lines I can send to management: URLs fixed, clicks protected, open items.
Finds page-one pages that get impressions but few clicks, compares them to your site-wide CTR, and rewrites their meta title and description around the queries that actually bring them traffic.
When to use itWhen your pages rank on page one and get impressions but few clicks, so your titles and descriptions are probably not convincing.
Matches GA4 landing-page performance against your WordPress menus, flags valuable pages missing from the navbar, dead weight and broken links, and proposes a leaner main menu.
When to use itWhen your site menu feels cluttered or outdated and you suspect it does not point visitors to the pages that actually bring conversions.
A plugin-by-plugin action list that flags outdated, duplicate and conflicting plugins and double-firing tags.
When to use itWhen your WordPress site has too many plugins, updates piling up, or you fear duplicate tags are inflating the conversions your ads optimize toward.