inemaSEO 7 — Systems: build your own open Semrush|INEMA.CLUB-PRO

Lesson 4 · 17 min

gsc-historico: Search Console forever

Search Console keeps 16 months. Two years from now, the week your site started being found by people who don't know your brand will be gone. gsc-historico imports the weekly CSV into a local database that never deletes anything and builds the report that matters: branded, non-branded and anonymized, what went up, what went down, and the content backlog.

Start the lesson
Wooden drawer file cabinet with cataloged index cards, one drawer open, in a library.

In this lesson you will

  1. 1Where the CSV comes from and what "anonymized" means
  2. 2Import without duplicating and generate the report
  3. 3Read the weekly series and the up/down
  4. 4Content backlog and pages with no clicks: the tool's rules, not Google's

Goal: import the weekly CSVs into a database that doesn't delete, and read branded × non-branded × anonymized, the content backlog and the pages with no clicks.

01From Search Console to the history

Every week, the same path. Click each step.

Click each block in the diagram to see what it does.

The data is Google's; the long-term memory is yours.

02Read what the report shows

Click each list.

1. Series

Branded is people who already know you. Non-branded is new people arriving through the topic. Anonymized is what Google hides because it is rare: total minus branded minus non-branded.

Track non-branded impressions and clicks, week by week.

Real INEMA caseinema.club, from 09/16–22 to 10/05–11: non-branded impressions went from 8 to 157 and non-branded queries from 3 to 51, with 0 non-branded clicks. The first 2 non-branded clicks came on inema.pro (2/293), driven by "curso jev".

03Import and generate the report

Run it from the ferramentas/gsc-historico folder. The example uses the real inemaSEO CSVs that come in the repository.

Terminal · import (folder or files)
cd ferramentas/gsc-historico
python3 gsc_historico.py importar ../../exemplos/gsc-historico/entrada --db dados/gsc.sqlite
Terminal · report for one site
python3 gsc_historico.py relatorio --db dados/gsc.sqlite --site inema.club --saida saida/inema.club
# another comparison: --atual YYYY-MM-DD --anterior YYYY-MM-DD
Terminal · every week, with your CSVs
# after gsc_semanal.py (inemaseo-metodo), point to its folder
python3 gsc_historico.py importar ~/path/to/gsc-folder --db dados/gsc.sqlite
python3 gsc_historico.py relatorio --db dados/gsc.sqlite --site <yoursite.com> --saida saida/<yoursite.com>
Template · API mode (uses the Google API; not run in this course)
# runs gsc_semanal.py with your credential (gcloud) and imports; not tested live by the author
python3 gsc_historico.py puxar --script ~/projetos/inemaseo-metodo/tools/gsc_semanal.py --pasta dados/gsc-csv
Example from the repository
importado: 10 linha(s) de resumo, 244 linha(s) de consulta → dados/gsc.sqlite
inema.club semana 2026-10-11 (comparada com 2026-10-04): sem marca 0 cliques / 157 impr.; subiram 15, caíram 15, pauta 18, páginas sem clique 5 → saida/inema.club/relatorio.html
inema.pro semana 2026-10-11 (comparada com 2026-10-04): sem marca 2 cliques / 293 impr.; subiram 15, caíram 5, pauta 6, páginas sem clique 6 → saida/inema.pro/relatorio.html

04Practice: your history

No CSV of your own yet? Do it with the example and come back when gsc_semanal.py runs.

E1 · Import and generate

15 min

Import the example folder (or your CSVs) and generate the report for one site.

Done when: the terminal shows the line "semana … sem marca … pauta …" and relatorio.html opens with the weekly series.

E2 · Three backlog decisions

20 min

Pick 3 queries from the content backlog and decide for each: write a new page or improve the one that already appears (today's page column).

Done when: 3 lines with the query, the decision (new or improve) and the URL of the page you would create or change.

05Test what you learned

The explanation shows up after your answer.

Question 1 of 4

Why store Search Console in a local database?skill

06Takeaways

MemoryWeekly CSV → SQLite that never deletes; re-importing doesn't duplicate.
The numberNon-branded, week by week; anonymized explains the difference.
Content backlogTool heuristic: check the page that already appears before writing another.

Going further

Previous lessonNext lesson