Best for
- Designers who own a live site and need a review they can act on, not a score.
- Product managers who need to know what regressed since launch, page by page.
Connectors
Neither connector is needed for the review itself. Connect them for the routine
version in Make it work for you.
Before you start
Have the public URL, and name the pages that matter most. Decide what you want out of this pass: a list of findings to hand to whoever owns the code, or fixes applied directly. Only the second needs the site open as a Replit project.Prompt the agent
What to expect
Agent works through the angles in the order you gave them, and reports what it covered: the pages it walked and the links it resolved. Each angle comes back as its own section. Every finding names the page, the issue, and the change to make. The review closes with the fix Agent would do first. For recurring link checks, use the routine prompt in Make it work for you. The routine is optional: the one-time review above does not need Slack or Notion.1
Connect your tools for recurring reviews
If you choose the weekly routine, Agent prompts you to connect Slack and Notion
if needed. Specify the public pages to check, the Slack channel, and the Notion log.
2
Review and create the routine
Agent opens New routine with the title, schedule, time zone, and prompt filled in.
Check Monday at 9:00 in your time zone and confirm the scope is recurring link checks,
not automatic website edits. Select Create routine when the instructions are right.
3
Receive your weekly link review
Each run checks the agreed pages and reports broken links or changes since the previous
week. Findings go to Slack and the Notion log, with results in the same Replit chat.
Ask Agent to list any pages or interactions it couldn’t check.
4
Find the routine and check its runs
Open Routines in the Replit sidebar. Select the run count to expand the history,
use the play button to run it now, or use the switch to pause and resume the schedule.Open a reported page and follow the affected link before assigning a fix. Links behind
forms, checkout flows, or modals may need a separate pass; the routine does not edit or
publish the website.
Make it work for you
Troubleshooting
Links behind a checkout or a modal were never checked
Links behind a checkout or a modal were never checked
A crawl reaches the links present in the rendered page. Anything that only
appears after a form, a modal, or a payment step needs its own pass.
The layout and accessibility findings feel thin
The layout and accessibility findings feel thin
Name the pages and the viewport width you want checked, instead of leaving
the sample to Agent. Start with the pages that carry your main task.
The design feedback is generic
The design feedback is generic
Say what the page is for and who it’s for. Without the goal, a critique
defaults to layout advice that fits any site.
Related
When the review says the problem is the design itself.
Put everything on one system when the review finds drift.
For a published Replit app, audit crawlability, metadata, and markup with
one-click fixes.