Creating Pull Requests

Before you can create a pull request, make sure the following are in place:

• GitHub connected — Your GitHub account must be connected to Align. See Connecting GitHub for setup instructions.
• Repository linked — The repository that contains your site's code must be linked to the site in Align.
• Issues detected — You need to have run at least one scan that found fixable issues.

After running a scan, the right action panel displays all detected issues organized by category. Issues are grouped into four categories:

• Metadata — Title tags, meta descriptions, Open Graph tags.
• Schema — JSON-LD structured data issues.
• AI Readiness — Missing or incomplete llms.txt file.
• Authority — Topical gaps identified by the Authority Map.

Click the checkbox next to any issue to include it in the PR. You can select issues from multiple categories to bundle them into a single pull request.

For convenience, Align provides several bulk selection options:

• Select all — Selects every fixable issue across all categories.
• Select by category — Selects all issues within a single category (e.g., all Metadata issues).
• Individual selection — Pick specific issues one by one for fine-grained control.

You can mix and match — select an entire category and then deselect individual issues you want to skip.

After selecting issues, Align calculates a safety score displayed as a percentage. This score represents the AI agent's confidence that the selected fixes will produce correct, non-breaking changes.

A higher safety score means the changes are simpler and more predictable. A lower score means the fixes involve more complex modifications that you should review carefully. See Issue Selection & Safety for a detailed breakdown of safety score ranges.

Before creating the PR, click "Preview Diff" to see the exact file changes that will be included. The preview shows a standard diff view with additions highlighted in green and removals in red.

Review the diff to make sure the changes look correct. Pay special attention to:

• Modified file paths — are the right files being changed?
• Content accuracy — are the meta descriptions relevant?
• Schema validity — does the JSON-LD look correct?

Once you are satisfied with the preview, click "Create PR". A progress modal appears showing the status of the PR creation:

1. Generating fix code for each selected issue
2. Creating a new branch on your repository
3. Committing the changes
4. Opening the pull request on GitHub

When complete, the modal shows a success message with a direct link to the PR on GitHub. The PR title and description are automatically generated to describe all included fixes.

Each PR created by Align includes:

• Branch name — Named with the current date for easy identification (e.g., align/fixes-2025-01-15).
• Commits — Separate commits for each fix type (metadata, schema, AI readiness, authority) so you can review changes by category.
• Description — A detailed PR body listing every change made, which pages were modified, and what was fixed.

After the PR is created, navigate to GitHub to review it:

1. Open the PR link provided by Align
2. Review the diff for each changed file
3. Check that all changes look correct and complete
4. Merge the PR when you are satisfied

After merging, run a new scan in Align to verify the fixes. The PR Impact Reports will show whether the merged changes improved your scores.

Creating pull requests requires a Pro plan or above. Free plan users can view detected issues but cannot create PRs to fix them.

Pro plan users can create PRs with standard limits. Agency plan users get unlimited PR creation along with additional features like Weekly Plans and regression alerts.