Built for Websites

Website review with desktop and mobile capture

Point your agent at a live URL. ReviseMy captures the page, runs a website-specific checklist, and keeps human marks authoritative across viewports.

The problem

Marketing pages and landing sites get rebuilt by agents without a structured pass on above-the-fold clarity, navigation, or mobile breakpoints. Stakeholders comment in docs; nothing ties feedback to the actual rendered page.

How ReviseMy fits

Your agent opens a review with `type: website` so hints target above-the-fold story, nav, and viewports. Prefer server capture from a public URL; fall back to screenshots when the site is behind auth or only on localhost.

Review type: website · Exactly one ingest source per review

How to get pixels in

Review type chooses the website lens. Ingest chooses how the page gets captured. Use exactly one source per call — mix freely when capture is unavailable or you already have shots.

Live URL capture

capture_url Recommended

Best default for public sites. `capture_url: true` + `page_url` renders desktop and mobile server-side and defaults to `type: website`.

Screenshots

images

Use when the site is localhost, behind a VPN, or capture is down. Pass desktop + mobile shots yourself and set `type: website` so the checklist still matches.

HTML render

html

Static landing HTML or a saved page snapshot. Rendered like a document; pair with `type: website` for above-the-fold and nav hints.

PDF pages

pdf

Design comps or multi-page site mockups exported as PDF. Each page becomes a frame; keep `type: website` for the landing-page lens.

Features for websites review

Server-side desktop + mobile capture

No manual screenshot gymnastics. Pass the URL; ReviseMy renders and stores viewport captures so review and fixes stay tied to the live page.

Above-the-fold and nav lens

Website checklists focus on first-visit clarity, plain-language nav, and hero contrast — the questions a landing page review should ask first.

Guest share for stakeholders

Send a private guest link when a PM or client needs eyes on the capture. Their suggestions stay suggestions until you accept them into authoritative marks.

Multi-pass until approved

Request changes to spawn the next pass with `parent_id`. Agents read structured pins and never claim the site is done while status is pending.

Websites checklist

ReviseMy runs these checks as optional second-opinion hints. Your marks stay authoritative.

Above the fold: value proposition and next step without scrolling
Navigation labels in plain language; current section obvious
Heading structure and hero text contrast over imagery
Mobile viewport: no horizontal overflow, tap targets ~44×44px
One dominant CTA per view with outcome-focused labels

Sample prompts

Try saying these to your agent after connecting MCP from the homepage.

“Review this URL — capture desktop and mobile and share the review link.”
“Run a design checkup on our landing page before we ship.”
“Apply my website marks and open a new pass with updated captures.”

FAQ

Does ReviseMy capture both desktop and mobile?

Yes when you use `capture_url`. If you pass `images` instead, include both viewports yourself and set `type: website`.

What if the site is behind login?

Server capture needs a publicly reachable URL. Capture authenticated screens yourself as `images` with `type: website` — same marks and checklist, different ingest.

Can stakeholders comment without MCP?

Yes. Use the guest share link for suggestions. Your marks remain authoritative; guest notes are triaged by the review owner.

What about SEO and performance?

The checklist reminds reviewers that screenshots miss title tags, Open Graph, and load performance — implement against the live DOM, not the PNG alone.

Other review types

Connect your agent

Get a free try token on the homepage and copy MCP config for ChatGPT, Claude, Copilot, Cursor, or Grok. No account required for reviewers.

Try with your agent See how it works