How I built a free Search Console dashboard for many sites
If you run more than a handful of websites, Google Search Console gets tedious fast: one property at a time, one tab at a time, and no quick answer to "which of my sites lost traffic this week?". I wanted that answer on
If you run more than a handful of websites, Google Search Console gets tedious fast: one property at a time, one tab at a time, and no quick answer to "which of my sites lost traffic this week?". I wanted that answer on one screen, so I built allclicks, a free dashboard for Search Console data. This post is a short tour of how it works.
What it shows
Sign in with Google, and allclicks lists every Search Console property you have access to. For each site you get clicks, impressions, CTR and average position, with a comparison against the previous period. On top of that:
- Dropping and growing lists. The sites that lost or gained the most clicks, so you see problems first instead of hunting for them.
- Tags. Group sites (by client, niche or project) and look at a whole group at once, including its top queries and pages.
- List and card views. The list view is the default; the choice, and which blocks are folded, is remembered between visits.
It covers Search Console only. There is no GA4 in it, on purpose: the point is to stay small and fast.
How it is built
- Next.js 16 (App Router) and React 19, with Tailwind 4 for styling.
- Google Search Console API for the data. The app asks for read-only access and does not write anything to your properties.
- Server-side rendering with caching. Search Console responses are slow and rate-limited, so pages are cached and refreshed in the background instead of calling the API on every visit.
- Preferences in cookies, not in a database: view mode, sort order, folded blocks. The server reads them on the first request, so the page renders in the right state with no flicker.
- Tests and CI. Vitest with Testing Library for the components, and GitHub Actions running lint, type checks and tests on every push. Dependabot keeps the dependencies current.
What I learned
- Rate limits shape the architecture more than anything else. Caching and batching came before any visual polish.
- Remembering small preferences (a folded block, a sort order) makes a dashboard feel faster than any optimization.
- Keeping the scope narrow is a feature. Every extra data source doubles the screens, and the "many sites at once" idea gets lost.
Try it
allclicks is free: https://allclicks.net/?utm_source=devto&utm_medium=listing
If you are comparing tools, it is a free alternative to SEO Gets for Search Console analytics. Feedback and feature requests are welcome.
Alex
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.