seo-gtm-brain

A modular intelligence engine for SEO, competitor mapping and content strategy. Provides keyword clusters, competitive matrices, backlink frameworks, SQL schemas and dashboard templates to support analytics, automation and organic growth workflows.

This repository documents tools, datasets, and workflows supporting SEO, competitor intelligence and organic acquisition analysis.
The goal is to provide one clear source of truth for frameworks and future automation pipelines.

What this project includes

• Keyword clusters and intent mapping
• Competitor ecosystem mapping
• Backlink opportunity framework
• Deep competitive intelligence matrix
• Content strategy map for regulated onboarding and compliance
• Initial SQL schema for Supabase/Postgres
• Dashboard metrics blueprint (Grafana-ready)

Purpose

To provide a structured foundation for monitoring:

• organic growth signals
• competitor activity
• keyword movement
• authority trends
• indexing and technical SEO health
• content performance

## Repository Structure


/docs
project_overview.md
competitor_matrix.md
keyword_strategy.md
content_strategy.md
dashboard_design.md
sql_schema_reference.md

/data
keyword_clusters.xlsx
competitors.xlsx
ecosystem_map.xlsx
backlink_opportunities.xlsx

/sql
schema.sql
tables/
competitors.sql
keywords.sql
backlinks.sql

/dashboard
grafana_queries.md
metrics_definition.md

README.md
LICENSE
.gitignore

## Collaboration Guidelines

### Branching
- Use feature branches for any changes (`feature/keyword-update`, `feature/competitor-refresh`)
- Keep `main` stable and clean.

### Commits
- Use clear messages describing the change (e.g. "Add competitor links", "Update keyword clusters", "Refresh dashboard metrics").
- Group related changes into a single commit.

### Pull Requests
- Create a PR for any non-trivial changes.
- Add a short summary describing what was added or changed.
- Tag reviewers if collaborating.

### Data Updates
- Place all updated spreadsheets in `/data`.
- Do not modify datasets directly in SQL folders — generate from source sheets.
- Keep versions clean: update, commit, and annotate.

### Documentation
- Add explanations or deep notes in `/docs`.
- Keep README high-level and focused on navigation and purpose.

### Roadmap & Tasks
- Use GitHub Projects for roadmap-level items.
- Use Issues for specific tasks or data corrections.