Build a Simple Keyword Ranking Monitor with Python and a SERP API
The article discusses building a simple keyword ranking monitor with Python and a SERP API. The goal is to create a clean and practical script that can track keyword rankings and provide a daily CSV report. This script can be used as a starting point for SEO monitoring, competitor tracking, and content performance checks.
- ▪The script reads keywords from a text file and calls a SERP API for each keyword.
- ▪It extracts organic results, checks for a target domain, and records the ranking position.
- ▪The script saves a daily CSV snapshot and compares today's ranking with a previous snapshot.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/cecilia_hill_d7b1b8d510e7/build-a-simple-keyword-ranking-monitor-with-python-and-a-serp-api-146p |
| Publication time | Tue, 30 Jun 2026 08:10:41 +0000 |
| Retrieval time | 2026-06-30T08:24:24.649Z |
| Last seen | 2026-06-30T08:24:24.649Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | LlLRaIbPFCRf |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3969261) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Cecilia Hill Posted on Jun 30 Build a Simple Keyword Ranking Monitor with Python and a SERP API #python #api #seo #tutorial At some point, every SEO script starts with a small question: Where does my site rank for this keyword? Enter fullscreen mode Exit fullscreen mode Then the small question grows legs. You want to track 10 keywords. Then 100. Then multiple competitors. Then different countries. Then daily changes. Then someone asks for a CSV report every Monday.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
