GitHub Pages

Overview

GitHub Pages is a popular hosting solution for developers, technical blogs, documentation sites, and static sites built with tools like Jekyll, Hugo, or Eleventy. Orbitr's GitHub integration works at the repository level — agents can read your content files, commit new posts and pages, and update metadata directly in your repo, which then triggers your normal deploy pipeline.

This integration is designed for sites where content lives in version-controlled files. Rather than bypassing your workflow, Orbitr works within it: committing changes to a branch, following your file structure, and using the same frontmatter and content conventions your site already uses.

What Agents Can Do

• Publish new blog posts and content pages directly to your repository
• Update frontmatter metadata (titles, descriptions, tags) across existing content files
• Optimize headings and on-page content for target keywords
• Add and improve image alt text in your content files
• Audit your content library for thin pages, keyword gaps, and outdated posts
• Create internal linking improvements across your content
• Commit changes to a review branch for your approval before merging

Setup

1. Go to Settings → Integrations in your Orbitr dashboard
2. Click Connect next to GitHub
3. A popup will open redirecting you to GitHub's authorization screen
4. Log in with your GitHub account if prompted
5. Choose whether to grant access to all repositories or select specific ones
6. Select the repository that hosts your GitHub Pages site
7. You will be returned to Orbitr with your repository connected

Required Permissions

Orbitr requests access to read and write to the repositories you select:

• Repository contents — read existing files and commit new or updated content files
• Pull requests — create pull requests for content changes so you can review before merging (optional, based on your workflow preference)
• Repository metadata — read repository structure, branches, and file tree

Orbitr only accesses the specific repositories you grant access to. It does not access your GitHub account settings, private repositories you have not selected, or any repositories outside the scope you define during setup.

Which Agents Use This

• Content Agent — writes and commits new posts, pages, and content files to your repository
• Technical SEO Agent — audits content files for metadata completeness and SEO issues
• SEO Workflow Agent — coordinates content production workflows that result in committed changes
• Strategy Agent — analyzes your repository's content library to identify gaps and prioritize new topics