This product was not featured by Product Hunt yet.
It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).

Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

seo-console-mcp

One MCP server for Search Console, the App Store and Play

Most SEO tooling stops at Google. Products get found in four places: Search Console, the App Store, Google Play and WordPress.org. One MCP server across all of them. 43 tools: search analytics, index coverage, IndexNow, on-page audits, App Store listings checked against Apple's limits, Play installs and traffic sources, wp.org stats, Core Web Vitals. Every tool also runs from the shell, so results land in a file not a model's context. snapshot records all four so a later run can diff it.

Top comment

maker here. I built this because I was doing SEO and ASO work across four properties and kept hitting the same two problems. the first is that the consoles do not talk to each other. Search Console, App Store Connect, Play and wp.org each have their own dashboard, their own auth, their own idea of what a week means. answering "how did we do" meant four tabs and a lot of retyping. the second is worse and it is why snapshot exists. nobody can diff a dashboard against what it said three weeks ago. App Store Connect keeps no history of a subtitle once you overwrite it. so "did that change work" gets answered from memory, and memory is how something that got worse gets remembered as flat. snapshot writes every surface to one timestamped file, and compare_snapshots does the arithmetic between two. the CLI matters for the same reason. over MCP a result lands in a model's context and is gone. from the shell it lands in a file you can still read in September. a few things I learned building it that might save someone else the time. Apple indexes the app name, the subtitle and the hidden keyword field, and does not index the description at all, so tools that measure description length are measuring nothing. Apple's API has no aggregate star rating resource, only age ratings, so any rating you see came from the public iTunes endpoint and should say so. Google Play's bulk report CSVs are UTF-16 with a byte order mark. and Search Console silently truncates at rowLimit, which nearly had me conclude a product had no demand when the row I needed was one past the cut, so the tool now fetches rowLimit+1 and tells you when there is more. MIT, 28 tools, no key needed for the on-page audit, PageSpeed, IndexNow, keyword ideas or wp.org tools. happy to add a surface if you are measuring something it misses.

About seo-console-mcp on Product Hunt

“One MCP server for Search Console, the App Store and Play”

seo-console-mcp was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #145 on the daily leaderboard. Most SEO tooling stops at Google. Products get found in four places: Search Console, the App Store, Google Play and WordPress.org. One MCP server across all of them. 43 tools: search analytics, index coverage, IndexNow, on-page audits, App Store listings checked against Apple's limits, Play installs and traffic sources, wp.org stats, Core Web Vitals. Every tool also runs from the shell, so results land in a file not a model's context. snapshot records all four so a later run can diff it.

On the analytics side, seo-console-mcp competes within Analytics, SEO, Artificial Intelligence and GitHub — topics that collectively have 733.4k followers on Product Hunt. The dashboard above tracks how seo-console-mcp performed against the three products that launched closest to it on the same day.

Who hunted seo-console-mcp?

seo-console-mcp was hunted by Ibrahim Hajjaj. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.

For a complete overview of seo-console-mcp including community comment highlights and product details, visit the product overview.