SEO and audits

Pressroom includes SEO auditing, GEO (Generative Engine Optimization), and an automated PR pipeline that fixes issues and submits pull requests.

SEO audit

Run a technical SEO audit on any domain:

POST /api/audit/seo
{"domain": "example.com"}

What it checks

Technical SEO:

• Crawlability and indexability
• Title tags and meta descriptions (length, uniqueness)
• H1 presence and structure
• robots.txt configuration
• Schema markup (JSON-LD)
• Core Web Vitals indicators

GEO (Generative Engine Optimization):

Based on Princeton research, GEO measures how likely AI models are to cite your content. Nine visibility factors:

Factor	Impact
Source citations	+40-115% visibility
Statistics	+37%
Expert quotations	+30%
Authoritative tone	+25%
Clear explanations	+20%
Technical terminology	+18%
Vocabulary diversity	+15%
Fluency	+15-30%

AI bot access:

• Checks if GPTBot, ClaudeBot, PerplexityBot are blocked in robots.txt
• Blocking AI bots prevents citation in AI search results

E-E-A-T assessment:

• Expertise, Experience, Authority, Trustworthiness scoring
• Author attribution and credentials
• About pages and contact information

README audit

Audit GitHub README quality:

POST /api/audit/readme
{"repo": "owner/repo"}

Checks for completeness, clarity, installation instructions, usage examples, and contribution guidelines.

SEO PR pipeline

The most powerful audit feature: automatically fixes SEO issues and opens a pull request.

How it works

Audit domain → Analyze with Claude → Plan fixes → Generate code → Open PR → Monitor CI

Starting a run

POST /api/seo-pr/run
{
  "repo_url": "https://github.com/owner/repo",
  "domain": "example.com",
  "base_branch": "main"
}

Pipeline stages

1. Audit — Run SEO audit on the domain
2. Analyze — Claude analyzes findings and identifies fixable issues
3. Plan — Generate a tiered fix plan:
   • P0 — Critical (blocking crawl, missing meta, broken schema)
   • P1 — Important (missing alt text, thin descriptions, heading structure)
   • P2 — Nice-to-have (schema enrichment, FAQ markup, performance hints)
4. Generate — Create code changes for each fix
5. PR — Open a GitHub pull request with the changes
6. Monitor — Watch CI/CD for pass/fail
7. Heal — If CI fails, analyze the error and attempt a fix

Checking status

GET /api/seo-pr/runs/{run_id}

Returns status, plan, PR URL, and deployment log.

Audit history

All audit results are persisted:

GET /api/audit/history?audit_type=seo&limit=20

Track SEO score over time to measure improvement.

Scoreboard

Compare all orgs by SEO score and content activity:

GET /api/scoreboard

Returns orgs ranked by SEO score, AI citability, signal count, published content count, and last active date.