PR Impact Reports

After you merge a pull request created by Align, the platform tracks whether the changes actually improved your site. PR Impact Reports show the before-and-after effect of each PR on your SEO score and keyword rankings.

When Align creates a PR to fix an issue, it records which issues the PR addresses. After you merge the PR and run your next scan, Align compares the old scan results with the new ones to verify whether each fix was successful.

The verification flow:

1. PR is created with specific fixes
2. You review and merge the PR on GitHub
3. Next scan runs on your site
4. Align checks if the fixed issues are resolved
5. Each issue gets a verification status

Each issue fixed by a PR displays a colored badge indicating its current status:

• Verified Fixed — The issue is no longer present. The fix worked.
• Fix Failed — The PR was merged but the issue persists. The fix may need adjustment.
• PR Open — The PR hasn't been merged yet. Merge it to apply the fixes.
• Awaiting Verification — The PR is merged but the next scan hasn't run yet. Run a scan to verify.

The Rankings tab includes a PR Impact section that shows which merged PRs improved specific keyword rankings. For each impacted keyword, you can see:

• The keyword and its current position
• Position change after the PR was merged
• Which PR caused the improvement
• The SEO score delta (before vs after)

In the Growth tab, PR Impact Reports show the SEO score change associated with each merged PR. This helps you understand which types of fixes have the biggest impact on your overall score.

For example, a PR that adds missing meta descriptions might show a +3 point improvement, while a PR adding JSON-LD schemas might show +5 points.

If a fix shows as "Fix Failed," it means the issue is still present after the PR was merged. Common reasons:

• The fix targeted a different page than what the scan checks
• A build or deploy step overwrote the changes
• The fix was correct but the page needs a cache refresh