GitHub fix pull requests
Connect GitHub and pick the repo for a site. whywontai opens a pull request built from your latest scan. You review the changes and merge them.
Why it matters
A report does not change a site. The time between a finding and a shipped fix is where most audits stop. A pull request puts the fix in the place where you already review and release code.
whywontai builds the pull request from your latest scan. Nothing changes on your site until you merge it. You can read each file, edit it and merge it on your own schedule.
How it works
- 01
Connect GitHub and pick the repo for your site.
- 02
Pick the fixes to include from your latest scan.
- 03
Review the pull request in GitHub, then merge it.
What you get
- A WHYWONTAI-FIXES.md file with every issue from your latest scan.
- An llms.txt file, only if your site has none.
- robots.txt changes that let GPTBot, ClaudeBot and PerplexityBot in, if your scan found them blocked.
- An IndexNow key file, so you can send changed pages to Bing.
- On Pro and Agency: static twins, comparison page drafts and article drafts.
When to use it
- Your site code is in a GitHub repo, including a repo that an app builder syncs.
- Your scan found blocked AI crawlers, a missing llms.txt file or pages that are empty for crawlers.
- You want fixes that you can review line by line before they go live.
Plans
| Fix pull requests a month | Free | Starter | Pro | Agency |
|---|---|---|---|---|
| GitHub fix pull requests | Not included | 4 | 20 | 100 |
Questions
- Does whywontai merge changes for me?
- No. It opens a pull request. You review it and merge it in GitHub.
- Does it work with Lovable, Bolt and Replit?
- It works with any site whose code is in a GitHub repo. Many app builders sync the project to GitHub.