Shahid Ali SEO Tools
Tools that run on your side, not on my server
Shahid Ali SEO Tools is a free set of Google Search Console checks that never touch a server of mine. These are the checks I run daily on client properties, rebuilt so you can run them on your own. Some run in your browser tab; one installs on your machine and gives your AI assistant the same access. Either way, the work happens on your side and nothing is kept. There is no signup here, no free tier, and no email wall, because none of them cost me anything to give away.
Runs in your browser
Two of the four connect to Search Console: you sign in to Google in the tab, read only, and closing the tab ends it. The health check and the robots.txt tester need nothing at all.
find, validate and test any sitemap, no login
Sitemap checker and validator
Type a domain and it finds every sitemap, follows the indexes, validates the XML and the protocol limits, checks each listed URL, lastmod, hreflang, image, video and news entries, and opens a sample of the live pages. Every finding comes with the fix and a guide. Nothing to connect, nothing stored.
Open the tool →noindex and canonical checker
Indexability checker
Paste a page, or up to 25, and see whether Google may index it: status and redirect chain, robots.txt, meta robots, X-Robots-Tag, canonical and its target, hreflang, and what Googlebot gets versus a browser. One verdict, the main reason first, a fix for each finding. Nothing stored.
Open the tool →googlebot, bingbot and the ai crawlers
Robots.txt tester
Type a domain and test its live robots.txt against Googlebot, Bingbot, the AI search bots from ChatGPT, Claude and Perplexity, the AI training bots, or any crawler you name. See the exact rule that decides, and get a copy-paste fix. Nothing to connect, nothing stored.
Open the tool →and llms.txt checker
llms.txt generator
Type a domain and get an llms.txt drafted from your menu, sitemap and page titles, then rename, reorder and trim it before you download it. The checker tab validates any live or pasted llms.txt and tests a sample of its links against robots.txt. Nothing stored.
Open the tool →is a page ready for ai search?
AI visibility checker
Paste a page and get a score out of 100 for how ready it is for ChatGPT, Perplexity, Claude and AI Overviews: AI crawler access in robots.txt and through the firewall, content in the raw HTML, schema and trust signals, and answers a machine can quote. Top three fixes first. It scores readiness, not citations, and says so. Nothing stored.
Open the tool →index status for a whole list, CSV or sitemap
Bulk index checker
Sign in to Search Console for the real index status of hundreds of URLs, or skip the sign-in and check any list for noindex, robots.txt, canonical and status code problems. Filterable table, a fix guide per row, CSV export. No site: guesswork.
Open the tool →what share of your sitemap is indexed
Sitemap index coverage checker
Reads your XML sitemap, inspects every URL through the same official API, and rolls it up into one number: the share Google actually kept. Sitemap indexes get a per-child breakdown that shows which sitemap is dragging the average.
Open the tool →not built yet
What comes next
The shortlist is a bulk redirect and canonical tester, browser-only in the same way. If you would find something else more useful, say so and it moves up the list.
Tell me what to build →Runs on your machine
Installs locally and talks to Google from there. It can submit, which the browser tools deliberately cannot.
What the app does with your Google account
The two Search Console tools above are Shahid Ali SEO Tools, and they ask Google for a single permission: read-only access to the Search Console properties you already own. They use it to call the official URL Inspection API on the URLs you give them, and for nothing else. They cannot submit a sitemap, request indexing, or change a setting on your property, because read-only access does not allow any of that.
The access token stays in the browser tab for as long as that tab is open, and is never written to local storage, a cookie, or a server of mine. Closing the tab ends the session. The URLs you inspect and the results that come back never leave your machine, because there is no server of mine in the path: the page talks to Google directly from your browser. Theprivacy page states the same thing in full.
The MCP server is a separate program, not part of this web app. It runs on your own machine under its own sign-in, which is how it can do the thing the browser tools cannot: request indexing, andits own page states what it stores and where.
If the tool tells you something is wrong
A status is a symptom, not a diagnosis. The guides explain what each one means and what actually fixes it, the case studies show the same statuses being cleared on real sites, and the indexing service is the version where I do it for you.