Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Epic] SEO growth: from 500 to 200k impressions and 50k clicks

Abierto
#18 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@anurag629 ya está trabajando en esto.

Desde el 10/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

epic seo

Goal

Grow tools.codercops.com from ~500 to ~200k monthly impressions and ~50k clicks.

Clicks are the real target; impressions are the byproduct. For a privacy-first tools microsite the levers are high-volume and long-tail developer-tool queries, guide content clustered around each tool, top-5 rankings, and click-worthy titles. Branded search is weak here and local SEO does not apply. Client analytics stays off per our privacy stance (see CONTRIBUTING.md), so Google Search Console and Bing Webmaster Tools are the scoreboard.

Growth model

  • Coverage: more indexed, ranking pages (guides plus optimized tool pages).
  • Position: push existing pages from page 2-3 into positions 1-5.
  • Click capture: keyword-led titles, FAQs, and rich results.

Phases

Tracked as sub-issues below:

  • Phase 0: Foundation and measurement
  • Phase 1: On-page quick wins
  • Phase 2: Coverage engine (guides and internal linking)
  • Phase 3: Authority and off-page
  • Phase 4: Compound and technical polish

Weekly scoreboard (GSC)

  • Total impressions and clicks
  • Average CTR
  • Queries in positions 1-3 / 4-10 / 11-20
  • Indexed page count
  • Top gaining and losing pages

How to contribute

Tasks labeled good first issue / help wanted are open to anyone. Tasks labeled admin-only need repo admin or an external account and are handled by a maintainer.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
9
Merge medio
9 h 50 min
PR fusionados (30 d)
105

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codercops/toolbelt

Todos los issues de codercops/toolbelt

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.