Launch the new site. Keep the traffic.
A redesign, a new CMS or a domain move is where traffic quietly disappears. Ask an AI agent which old URLs lost clicks, which new ones aren't indexed and what Google and Bing see, the week after launch.
Free plan, 7-day Pro trial, no card required.
| Old URL | Clicks | New URL status |
|---|---|---|
| /services/seo.html | −82% | Not indexed |
| /blog/2023/guide | −64% | Redirects to /blog |
| /pricing.html | −9% | Indexed |
Example data for illustration.
GSC Magic gives technical SEOs and web studios Search Console, Bing Webmaster Tools and Core Web Vitals in Claude, ChatGPT or Cursor: batch URL Inspection, index health across sitemaps, before-and-after comparisons by page, crawl issues on Bing, PageSpeed audits and IndexNow submission, the checks that decide whether a migration keeps its traffic.
Sound familiar?
Migrations fail quietly
Redirect maps miss pages, new URLs wait to be indexed and the traffic loss shows up in reports weeks after launch.
Inspection one URL at a time
The Search Console interface inspects single URLs. Checking a few hundred key pages after a launch is a day of clicking.
Two engines, two dashboards
Google and Bing report crawl and index problems in different places, in different words.
What you get
Before-and-after by page
Compare clicks and positions for the weeks before and after launch, per old and new URL, and find what was lost.
Batch URL Inspection
Inspect lists of URLs and get index status, canonical and the reason Google gives, grouped for the report.
Index health across sitemaps
Sitemap status, submitted vs indexed and index problems by reason, with sitemap resubmission on Pro.
Bing crawl issues
Crawl stats and crawl issues from Bing Webmaster Tools, and IndexNow to get new URLs discovered quickly.
Core Web Vitals per template
Field data from the Chrome UX Report per URL or origin, its history, and a PageSpeed Insights run for the details.
Works where you work
Cursor, Claude Code or VS Code next to the code, Claude or ChatGPT for the report, and gsm_ tokens for scripts.
Up and running in a minute
- 1
Connect before you launch
Import the site so the pre-launch baseline is stored. Pro backfills 16 months on connect.
- 2
Add your tools
Claude Code or Cursor for the team, Claude or ChatGPT for reporting. Add a Bing key for Bing data.
- 3
Check daily after launch
"Which top-100 old URLs lost clicks since launch, and is the new URL indexed?"
Prompts to try
Copy one into Claude, ChatGPT or your editor once GSC Magic is connected.
Compare clicks per URL for the two weeks before and after our launch on [date]. List the biggest losers.
Inspect these 50 URLs and group them by index status and the reason Google gives.
Which URLs in the new sitemap are submitted but not indexed?
List crawl issues Bing reports for the new site and suggest a fix for each type.
Compare mobile Core Web Vitals for the old and the new homepage template.
Submit every URL from the new sitemap to IndexNow and resubmit the sitemap in Search Console.
The plan that fits
Migrations need the baseline stored before launch and room for a lot of checks after it. Pro keeps history, has no call limits and adds sitemap and IndexNow writes. Studios with several people and client sites usually take Agency for 5 seats.
Compare all plans →Pro
For site owners, marketers and consultants.
- Stored baseline and 16 months of history
- Unlimited batch inspections and reports
- Sitemap resubmission and IndexNow
- Up to 10 sites; 25 and team seats on Agency
Questions
Can it check redirects?
It shows what Google reports for each URL (index status, canonical, the reason a page is not indexed) and how clicks moved between old and new URLs. It does not crawl your redirect map itself; pair it with your crawler for that.
Is URL inspection limited?
Google's URL Inspection API has a daily quota per property, which applies whichever tool calls it. GSC Magic batches requests and reports what it could check.
Can I use it for client migrations?
Yes. Import each client site with the Google account that has access. Agency adds client groups, so each team member only sees the sites they work on.
Does it work from the terminal?
Yes. Claude Code and Cursor connect with OAuth, and scripts can use a read-only gsm_ token over Streamable HTTP.
Will it change anything on the site?
It never edits the site. Write tools only submit sitemaps and URLs to search engines on paid plans, and you can switch them off in Settings.
Also built for
Developers
Search Console, Bing and Core Web Vitals in Claude Code, Cursor and VS Code. Check indexing after every deploy.
See how it works →SEO analysts
Cannibalization, decay, CTR outliers and 16 months of kept history, without the spreadsheet.
See how it works →Agencies
Up to 25 client sites, 5 team seats, client groups and monthly client reports.
See how it works →Online stores
Product and category pages: indexing, seasonality, Core Web Vitals and revenue pages that slip, from your own data.
See how it works →