Post-redesign check: old URLs with traffic that now break
Rebuilds the pre-launch page list from Search Console, checks each old URL live, maps broken ones to the closest new page by topic and intent, and creates 301 redirects on the hosting server only after approval.
When to use it
When a site has just been relaunched or redesigned and old URLs that used to get search traffic may now be broken.
What you get
A redirect map of old URLs to the closest new pages, 301 redirects created on the server after your approval, then verified and the sitemap resubmitted.
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.
Client site [client domain] was relaunched on our hosting server on [launch date]. Use Search Console property [client property]. If the server hosts more than one site, the site key is [site key].
1. Pull every page that had clicks or impressions in the 90 days before the launch date. Use get_report with platform=search_console, start_date and end_date set to that window, at page level (check describe for search_console if you are unsure of the level name). If that window cannot be read, fall back to gsc_performance with dimension=page and enough days to reach back before the launch, and tell me the totals then include post-launch data. Search Console keeps about 16 months, so say so if the window is older than that.
2. Fetch each of these URLs live with site_read_url and record the HTTP status code and, for redirects, the Location header.
3. Read the redirects that already exist with site_redirects (mode=list).
4. To understand the new site, list its pages with site_list_files and read the relevant ones with site_read_file, or with site_read_url outline=true for title and headings.
Deliver a table with these columns: old URL, clicks, impressions, current status (200, 301, 404 or other), existing redirect target, proposed new URL.
To choose the proposed new URL, match on topic and intent, not just slug similarity. Point to the closest equivalent page, never blanket-redirect to the homepage. Mark any URL with no sensible equivalent as "let 404". Also flag redirect chains (an old URL whose target redirects again) and redirects that land on a non-200 page, and propose the direct fix.
Show me the full redirect map, then run site_redirects with mode=add and confirm=false so I see the exact preview. Wait for my approval before calling it with confirm=true.
After I approve and the redirects go live:
- re-fetch each old URL with site_read_url and confirm it returns a 301 to the right target
- inspect the target URLs with gsc_inspect_urls in batches of up to 20, highest-traffic old URLs first. If the quota runs out, tell me which ones are left so we continue later
- read the current sitemaps with gsc_sitemaps, propose resubmitting the right one, and wait for my confirmation before calling gsc_submit_sitemap
Uses 90 days of converting Google Ads and Microsoft Ads search terms to find topics where you pay for conversions but have weak or no organic visibility. Returns a prioritized content plan and a preview-only list of keyword additions.
When to use itWhen you pay for conversions on search terms but are unsure which topics deserve organic content so you can rely less on ads.
Clusters of the real Google Search and Maps queries behind your listing, compared with your services and categories, plus a previewed fix.
When to use itWhen your Business Profile gets views but you suspect your services and categories do not match what people really search for on Google and Maps.