AgenticSEO
integrations•6 min read

GitHub Integration

Manage content through your GitHub repository with automated pull requests and version control.

GitHub Integration

For developers and teams who manage content as code, the GitHub integration enables content updates through pull requests and automated workflows.

Overview

The GitHub integration is ideal for:

  • Technical teams using static site generators (Next.js, Gatsby, Hugo)
  • Content-as-code workflows where content lives in markdown files
  • Version control requirements for content changes
  • Review workflows using pull requests

How It Works

  1. Repository Connection - Link your GitHub repository to AgenticSEO
  2. Branch Creation - When content updates are needed, we create a feature branch
  3. Pull Request - Changes are submitted as a PR for your review
  4. Merge & Deploy - Once approved, changes merge and your CI/CD handles deployment

Connecting Your Repository

  1. Navigate to Settings → Integrations in AgenticSEO
  2. Click Connect GitHub
  3. Select the repository containing your content
  4. Configure the content directory path (e.g., src/content/blog/)
  5. Set your preferred branch naming convention

Configuration Options

# Example configuration
contentPath: src/content/blog/
baseBranch: main
branchPrefix: agenticseo/
commitMessage: "[AgenticSEO] {action}: {title}"
autoMerge: false

| Option | Description | Default | |--------|-------------|---------| | contentPath | Directory for content files | /content/ | | baseBranch | Target branch for PRs | main | | branchPrefix | Prefix for feature branches | agenticseo/ | | autoMerge | Merge PRs automatically | false |

Pull Request Format

Each PR created by AgenticSEO includes:

  • Clear title describing the content action
  • Detailed description with changes summary
  • Labels for easy filtering (agenticseo, content)
  • Diff preview showing exact changes

Supported Actions

  • ✅ Create new content files
  • ✅ Update existing content
  • ✅ Update frontmatter (titles, descriptions, meta)
  • ✅ Add internal links
  • ✅ Optimize content structure
  • ❌ Delete files (requires manual action)

Security

  • We use GitHub Apps with minimal required permissions
  • Only the specified repository is accessible
  • OAuth tokens are encrypted at rest
  • You can revoke access anytime from GitHub settings

Troubleshooting

Verify that:

  1. The GitHub App is still installed on your repository
  2. Branch protection rules allow the GitHub App to push
  3. The content path configuration matches your repository structure

Check your contentPath configuration in Settings → Integrations → GitHub. Make sure the path matches where your content files are stored.

What's Next?

Browse all docs