Technical SEO with your AI, from Google's data to the fix on your server
SEO tools look at your site from outside and hand you a list. SudoWhizzy gives your AI Google Search Console, Google Analytics 4, Core Web Vitals and your server's own access logs in one connection, so it can find the real cause and then fix it on the server: redirects, robots.txt, canonicals, sitemaps, caching. You approve every change.
Works with Claude, Claude Code, ChatGPT and Cursor.
How your AI does it
- STEP 1
It reads what crawlers really do
crawl_report reads your access logs: what Googlebot, Bingbot and AI crawlers fetched, which 404s and 5xx errors Google got, how much crawling went to filtered and query-string URLs, and which "Googlebots" were fake (reverse DNS). No outside tool can see this.
- STEP 2
It asks Google
Search Console for clicks, impressions and positions against the period before, URL Inspection for why a page is not indexed or which canonical Google picked, submitted sitemaps, and queries where your own pages compete. Google's update history tells it whether a drop lines up with a core update before it blames your site.
- STEP 3
It checks the pages
Status and redirect chains, titles and descriptions, canonicals, hreflang, headings, broken internal links, robots.txt tested the way Google reads it, a sitemap audit, structured data against schema.org and Google's rich-result rules, and real-user Core Web Vitals with a Lighthouse test for the slow pages.
- STEP 4
It checks the server
Time to first byte on the main page types, full page cache, compression and cache headers, one host and one protocol in a single 301, soft 404s, noindex leaks, and the Magento or WordPress SEO settings themselves.
- STEP 5
You get a ranked list, with evidence
Findings ordered by impact: errors and noindex leaks first, then crawl waste and canonicals, then speed. Each comes with numbers and example URLs, matched across Google's data and the server.
- STEP 6
It fixes what you choose
On the server, one change at a time with your approval: 301 redirect maps, robots.txt rules, canonical and rewrite settings, sitemap generation, cache and compression, image conversion. Titles, descriptions and new content are saved as drafts for you to review, never published unasked.
Questions it answers
- Why did my Google traffic drop last month?
- Which pages are not indexed, and why?
- Is Googlebot wasting its crawl on filter URLs?
- Which of my pages compete for the same keyword?
- Why is my LCP slow, and what does it cost?
- Are my product rich results eligible?
- How much traffic do ChatGPT and Perplexity send me?
- Which pages have impressions but almost no clicks?
The tools your AI gets
All through the same SudoWhizzy MCP address as your server tools. How to connect Google.
| Tool | What it does | Plan |
|---|---|---|
crawl_report | What Googlebot, Bingbot, AI crawlers and SEO bots really fetched, from your access logs: errors, crawl waste, fake Googlebots | Every plan |
gsc_performance_overview | Clicks, impressions, CTR and position against the period before, with the biggest winning and losing queries and pages | Starter and up |
gsc_search_analytics | Performance by query, page, country, device or date, with filters and two-period comparisons | Starter and up |
gsc_inspect_url | Google's own view of up to 20 URLs: indexed or not and why, last crawl, the canonical Google picked | Starter and up |
gsc_sitemaps | Submitted sitemaps with errors, warnings and when Google last read them | Starter and up |
gsc_cannibalization | Queries where two or more of your pages split the impressions and compete with each other | Pro and up |
google_updates | Google's core, spam and helpful content updates, to line up with traffic changes | Starter and up |
core_web_vitals | Real-user LCP, INP and CLS from the Chrome UX Report, 6 months of history, and a Lighthouse test with the causes | Starter and up |
validate_schema | Structured data checked against schema.org and Google's rich-result requirements | Starter and up |
page_audit | Status, redirect chains, titles, descriptions, canonicals, hreflang, headings, robots and issues for up to 10 URLs | Pro and up |
page_links | Every link on a page with anchor text and rel, and broken or redirecting internal links | Pro and up |
page_content | A page's main content as clean text, to review, compare with a competitor or rewrite | Pro and up |
robots_check | robots.txt tested the way Google reads it, for Googlebot, Bingbot and AI crawlers | Pro and up |
sitemap_check | Sitemaps audited: limits, lastmod, and a sample of URLs that should answer 200 and be their own canonical | Pro and up |
ga4_overview | Sessions, users, engagement, conversions and revenue against the period before, by channel, with organic search's share | Pro and up |
ga4_landing_pages | Landing pages with engagement, conversions and revenue, for organic search or any channel | Pro and up |
ga4_ai_traffic | Visits from ChatGPT, Perplexity, Gemini, Claude, Copilot and other AI assistants, and the pages they land on | Pro and up |
Start with this prompt
Paste it into your AI with SudoWhizzy connected. It fetches the matching playbook and explains its plan before changing anything.
Technical SEO audit from the server side · all prompts
The crawl report is on every plan, Free included. Search Console, Core Web Vitals, the schema validator and the Google update tracker are on every paid plan. Page audits, links, robots.txt, sitemap audits, cannibalization and Google Analytics 4 are on Pro and Agency. Starter: 3 properties, the last 30 days. Pro: 10 properties, the last 90 days. Agency: 25 properties, all 16 months Google keeps. Core Web Vitals checks a day: 100 on Starter, 300 on Pro, 1,000 on Agency. Pricing.
Questions
How is this different from an SEO tool's site audit?
An SEO tool crawls your site from outside and gives you a list to work through. Your AI here also reads your server's access logs, its configuration and its real response times, matches them with Google's own data, and can make the server-side fixes itself, with your approval.
Does it work with Semrush, Ahrefs or SE Ranking?
Yes. Attach an exported audit or report in the chat, or connect their own MCP connector in your AI client. Your AI combines it with Search Console and the server, and dismisses the issues that are not real.
Will it change my titles or publish content?
Not without you. Server fixes need your approval one by one. Titles, descriptions and new content are written as WordPress drafts or disabled Magento CMS pages for you to review.
Which Google permissions does it need?
Read-only access to Search Console, and to Google Analytics on Pro and Agency. Your AI cannot submit sitemaps, request indexing or change anything in your Google accounts; those stay with you.
Safety on every task: destructive actions wait for your approval, /etc is saved before changes, and every action is logged. How it works.
More your AI can do
Your Magento server, run by your AI
WordPress and WooCommerceA fast, secure WordPress server, run by your AI
Fresh VPSFrom an empty VPS to a secure web server, by asking
HardeningHarden your Linux server without locking yourself out
Hacked siteHacked shop or site? Find it, clean it, close the door
MigrationMove your site to a new server with minutes of downtime
Google Search Console MCPGoogle Search Console in your AI, with your server next to it
Google Analytics 4 MCPAsk your AI about your GA4 traffic, and see what AI assistants send you
Connect your first server
Start free with one server in read-only mode. Upgrade when you want your AI to fix things.
Get started