GitHub PR SEO Checklist

Last updated: May 19, 2026

Pull Request Checklist

Paste this into a GitHub PR description when the change affects a public URL, search appearance, internal linking, structured data, analytics event, or policy-sensitive copy.

# SEO PR Checklist

## Scope
- [ ] PR changes one clear page, tool, template, or workflow.
- [ ] The page solves a real user task, not a keyword variant.
- [ ] No fake traffic, ad clicking, ranking promise, or AdSense approval promise.
- [ ] Human reviewer can verify the changed URL from this PR description.

## Metadata
- [ ] Page has a unique title.
- [ ] Page has a useful meta description.
- [ ] Canonical URL matches the public route.
- [ ] Open Graph text is accurate if the layout defines it.
- [ ] The copy does not overpromise revenue, rankings, indexing, or AI visibility.

## Page Value
- [ ] Tool pages include input, output, limitations, FAQ, and related links.
- [ ] Guide pages include steps, examples, mistakes, FAQ, and related tools.
- [ ] Template pages include a copyable artifact and clear safe-use notes.
- [ ] Compliance-sensitive advice uses cautious language and next actions.

## Technical SEO
- [ ] Route returns 200 after build or deploy.
- [ ] The route is present in sitemap generation if it is public.
- [ ] robots.txt does not block the route.
- [ ] Internal links point to and from the new or updated page.
- [ ] Structured data is valid for the visible page content.
- [ ] No empty sections, placeholder text, broken links, or console errors.

## Analytics
- [ ] Tool copy/export/run actions are tracked only after a real user action.
- [ ] Event params do not include raw CSV rows, emails, account IDs, or secrets.
- [ ] No automation is used to inflate GA4 pageviews or tool usage events.

## Verification
- [ ] pnpm lint
- [ ] pnpm typecheck
- [ ] pnpm build
- [ ] pnpm siteops:health after deploy or against the intended base URL.

## Reviewer Notes
- Evidence:
- URLs checked:
- Remaining risk:
- Follow-up issue, if needed:

Issue Template

Use this shorter issue format when Hermes or a human review finds a search, indexing, analytics, or content quality task that should be split into its own PR.

# SEO change: [route or workflow]

## Reason

## Affected URL

## Evidence
- Search Console:
- GA4:
- Manual review:
- User or market signal:

## Proposed Change

## Acceptance Criteria
- [ ] User task is clear.
- [ ] Metadata and canonical are correct.
- [ ] Sitemap and internal links are updated.
- [ ] Safety language is present where needed.
- [ ] Verification commands pass.

## Safety Boundaries
- No artificial pageviews.
- No ad clicks or ad testing.
- No guaranteed ranking, revenue, approval, or AI Overview claims.
- Human review required before deploy.

Review Matrix

How It Fits The RedBit Workflow

Start with a real signal: a Search Console query, a sitemap issue, a tool usage gap, a manual content review, or a documented market pain. Turn the signal into a small issue, implement one useful change, then use this checklist before merging. After deployment, run pnpm siteops:health and inspect the affected URL.

Pair this with the Hermes SiteOps Monitoring Runbook for daily and weekly review loops, or use the Sitemap Checker when a new public route needs indexing triage.

FAQ