Point it at staging. Get a review-ready capture of the whole site.
RouteShot turns a day of manual screenshotting into one job you kick off in under a minute. Here is everything it does between "go" and a ZIP your reviewer can open.
Three steps, under a minute of your time.
Point at the URL
Drop in a project's staging URL. RouteShot discovers the sitemap automatically, or takes a manual list when there isn't one. Saved credentials are reused, so you never paste a staging password twice.
Capture the whole site
Every page, at your standard widths, desktop and mobile, full-page and above-the-fold. You watch live progress and walk away.
Download review-ready
An organized ZIP that drops into your routing tool with no renaming, and a record of exactly what ran.
It finds the pages. You don't hand-build URL lists.
RouteShot reads the site's sitemap, follows index files, and falls back to a manual URL list when a staging setup is unusual. The point is that you stop maintaining spreadsheets of URLs.
Real staging sitemaps are noisy. So discovery is filtered by rules you set once per project and never touch again:
- Child-sitemap selection. WordPress-style sitemap indexes split by content type. Keep the page sitemaps, drop the press-release and post archives. This one filter does most of the work.
- Path include / exclude. Patterns like
/investors/*or/news/*that you never route for review. - Locale exclusion. Drop
/sv/*and other language duplicates of the same pages.
670 URLs → 32 review-relevant English pages. On one pharma site, page-sitemap plus locale filtering dropped 477 press-release archives and 363 Swedish duplicates, leaving exactly the pages worth reviewing.
Every width that matters, standardized.
Set your org's default widths once. Everyone captures at the same sizes, so a review is reproducible and "which width did you use?" stops being a question.
Defaults ship at desktop 1140×900 and mobile 375×812. Swap in device presets, or enter fully custom width × height when a client is focused on a specific device. Each viewport can capture portrait, landscape, or both.
The details a generic screenshot tool misses.
ISI-aware full-page capture
Important Safety Information is handled the way review needs it: the sticky, minified ISI tray is hidden in the full-page shot, the in-flow full ISI at the bottom of the page is always included, and the expanded ISI state is captured as its own artifact. Turn ISI handling off per project and non-pharma sites pay zero cost for it.
Consent-state capture
The cookie banner and its settings panel are captured as first-class artifacts before dismissal.
Encrypted staging auth
Basic-auth credentials are saved once per project, write-only, never stored or logged in plaintext, and never read back.
Form states captured, without ever submitting one.
On a page with a real form, RouteShot captures the normal state, each custom dropdown open, and the submit-empty validation error state, all from the full-page shot.
It never submits the form or transmits any form data. Error states come from client-side validation only. That is a hard line: auto-submitting forms on regulated sites would push junk into client CRMs and lead pipelines. When you need the thank-you page, you attach its URL to the project and RouteShot captures it right after the form and orders it alongside, no fake submission required.
Nothing slips, and everything is on the record.
Failed pages are flagged and retried on their own, so one flaky page never forces a full re-run. Live counts update per page as the job runs. And every job records the actor, timestamp, URL set, and per-page outcome, so compliance questions always have receipts, kept even after the images are cleaned up.
Output that drops straight into routing.
A single ZIP organized desktop | mobile / full | above-fold, filenames carrying the page slug and viewport, so there is no renaming before it goes into your PDF or routing tool.
Next up: a compiled review PDF with a cover page, table of contents, and one labeled capture per page, the end-game deliverable for MLR routing.
On the roadmap.
These are not in v1. They are the direction, and the reason the capture engine is built the way it is.
- Deep capture. Interactive states: dropdowns open, accordions expanded, filled and validated form variants. The capability no generic tool has.
- Ziflow integration. Push the finished PDF straight into Ziflow as a proof, and sync the review decision back so the job record shows the real outcome.
- Monday.com integration. A status change on your board triggers a capture; on completion RouteShot posts the result back to the same item.
See it on one of your sites
Request access and we'll run a capture on a live project so you can judge the output yourself.