Deeper dives
How to re-roast a page after making changes and use the diff comparison to measure exactly what improved and what still needs work.
Last updated May 10, 2026
Re-roasting lets you run a second (or third, or fourth) roast on the same page after you have made changes. PageScorch keeps every roast result and shows you a side-by-side diff between versions so you can see exactly what changed.
This turns PageScorch into a feedback loop rather than a one-time audit. You roast, fix, re-roast, and confirm the fix worked.
From any completed roast result page, find the Re-roast button. This creates a new roast for the same page:
The re-roast runs through the same analysis pipeline and returns a new score, problem list, and fix suggestions.
After re-roasting, PageScorch displays a comparison between the original roast and the new one:
Score change — the new score is shown alongside the original. An increase means the changes improved conversion readiness. A decrease (rare but possible) means something in the update introduced new problems.
Resolved problems — problems from the original roast that no longer appear in the new result. These are your confirmed wins.
Remaining problems — problems that appeared in both the original and the new roast. These are still affecting your score and need attention.
New problems — problems that appear in the new roast but were not in the original. This can happen when a redesign fixes one issue but introduces another.
A successful round of fixes typically produces:
If the score did not move at all and no problems were resolved, the changes did not address the specific friction points the AI identified. Go back to the problem list and apply the high-priority items first.
When you re-roast, the new result is linked to the original roast and shown in the diff view. If you start a completely new roast (e.g. by uploading a fresh screenshot from the main dashboard), it is treated as an independent roast with no connection to the previous one.
Use re-roast when you want to track improvement on the same page over time. Use a new roast when you are auditing a different page or want a clean baseline.
Each re-roast uses one roast credit, the same as a standard roast. The diff comparison itself does not use an additional credit — it is displayed automatically once a re-roast exists.
If you are doing agency work, the diff view is a useful deliverable. It shows the client measurable before/after evidence of the improvements made. You can share the result URL directly or include the score change and resolved problems in a client report.
See White-label reports and custom notes for how to customize reports before sending them to clients.
Still stuck?
Email hello@pagescorch.com and we'll help you sort it out.
On this page