DEV Community

glq0546
glq0546

Posted on

How I Built a GSC Diagnostic Micro-SaaS with Next.js and Vercel in a Weekend

Hey Devs,

As an indie hacker, I got tired of manually digging through Google Search Console every week to find "striking distance" keywords (rankings 11-20) and indexing issues.

So this weekend, I decided to build a micro-SaaS to automate it. I wanted to share the stack I used and the result.

The Stack

  • Next.js (App Router): For both the frontend UI and the Serverless API routes.
  • Tailwind CSS: For the dark mode dashboard UI.
  • Google Search Console API: Using googleapis to fetch real GSC data.
  • Vercel: For deployment (super easy with the built-in env variables for Google credentials).

How it works

The tool connects to the GSC API and applies a segmented CTR model to estimate the potential traffic lift if a page moves from position 15 to the top 3. It also checks indexing status via the URL Inspection API.

It took a bit of wrestling with the Google OAuth flow and Vercel environment variables, but it's finally live.

You can check out the MVP here: https://gsc-mcp-core.vercel.app/
(Note: It's currently running on my personal OAuth credentials for the demo, so it might only fetch my site's data for now. Working on multi-tenant auth next!)

Would love to hear your thoughts on the UI or the Next.js architecture!

Top comments (0)