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
Sign in to Google in the tab. Read only, and closing the tab ends it.
index status for a whole list or sitemap
Bulk Google index checker
Runs the official Search Console URL Inspection API over hundreds of URLs at once and returns a filterable table: indexed, crawled but not indexed, discovered, unknown, blocked. No site: guesswork, and export to CSV.
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 browser 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.