# Build brief — a focused alternative to Semrush

> **Verdict:** Not faithfully · **Buildability:** 18/100 · **Category:** SEO Marketing
> **Source:** https://www.canitbevibecoded.com/semrush
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Semrush. Verify current pricing and capabilities before acting.

## Context

**Semrush** — SEO, PPC, content, competitive research, and AI visibility toolkit. It currently costs $139.95/mo.

You can build small audits and rank trackers, but Semrush's moat is massive keyword, competitor, backlink, PPC, and SERP datasets plus integrations and reports.

This brief describes a focused, single-operator replacement for the part of Semrush that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Crawl a site, track selected keywords with an API, collect Google Search Console data, and generate reports.

- Automate a bounded research or reporting workflow using permitted data sources.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Crawler.
- GSC/GA integrations.
- Database.
- Rank tracking infrastructure.
- Reporting UI.

### Data and integrations

- Search APIs.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a rank-and-health tracker for sites I own, covering the
self-collectable slice of Semrush. Requirements:

- A Node CLI on a nightly cron: better-sqlite3 for history, and a static HTML
  report regenerated each run.
- Track 20-50 chosen keywords through a SERP API (Serper or DataForSEO, key in
  .env); store position per keyword per day and draw movement sparklines in the
  report.
- Pull clicks, impressions, and average position per query from the Google
  Search Console API for my own properties (OAuth creds in .env).
- A technical crawl of my own site with crawlee: broken links, missing titles
  and descriptions, redirect chains, slow pages, as a table in the report.
- Email the report weekly via Resend (key in .env), but only when something
  moved: a position swing over 3 places or new 404s.
- No accounts, no telemetry; all history lives in one SQLite file.
- Out of scope: competitor keyword gaps, backlink databases, and traffic
  estimates for sites I do not own. Do not scrape or estimate third-party data.
- README: the cheapest SERP API tier for daily checks, the GSC OAuth steps, and
  a note that Semrush's moat is years of crawled keyword, backlink, and SERP
  data no solo build can collect; this tracks only what I own.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Keyword database.
- Competitor intelligence.
- Backlink/PPC data.
- AI visibility data.
- The useful dataset is owned, accumulated, or expensive to reproduce.
- Reliability at the vendor's scale is an operations problem, not a prompt.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [SEO Macroscope](https://github.com/smac89/SEO-Macroscope) — Open-source technical SEO crawler; useful only for a narrow slice of Semrush

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/semrush