Team markers

Pin it, tag it, hand it over.

Automated checks catch the mechanical issues. Markers handle the rest: pin anything onto a scanned page, @mention whoever needs to fix it, and keep the whole conversation where the issue is.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required

Updated

Why markers

Not every issue is a failed check.

Plenty of what you find in a review needs a person to judge it, and someone else to fix it.

  1. 01

    Judgement calls

    Copy that's technically fine but wrong for the brand, a crop that feels off, an English placeholder like “TBC”.

  2. 02

    Lost in Slack

    Screenshots with circles on them, pasted into a thread, buried by lunchtime.

  3. 03

    Unclear ownership

    Everyone saw the issue. Nobody knew it was theirs to fix.

How it works

From spotted to sorted, on the page itself.

  1. 01Pin

    Drop a marker exactly where the issue is

    Open any page in a scan and add a marker on the spot. Give it a priority and an issue type so it's clear how urgent it is and what kind of fix it needs.

  2. 02Mention

    @mention whoever needs to pick it up

    Tag a teammate in a comment and they're notified in the app or by email, depending on their settings. Reply, edit or delete as the fix goes in.

    • Comment on any marker
    • Edit or delete as things change
    • Notifications in the app or by email
  3. 03Filter

    See what matters first

    Filter markers by high or low priority, or by type of issue, so a developer can see their design fixes and a copywriter can see theirs.

    How scoring works

Frequently asked questions about team markers

  • Any team member assigned to the project can add markers to a scanned page.

  • Yes. You can comment on any marker, and edit or delete markers as the work moves on.

  • Yes, when you @mention them in a comment. They're notified in the app and/or by email, depending on their notification settings.

  • No. Each scan starts with a clean slate, so markers always relate to the version of the site that was scanned.

  • Only if you choose. Markers are internal to your team by default, so you can be candid about what needs fixing. When you share a report with a client, you decide whether your markers are included.

  • Yes. Filter by high or low priority, or by type of issue.

Explore Frank

See what else Frank does for you.

  1. 01

    Accessibility checks

    Frank flags missing alt text and common accessibility issues on every page, from skipped heading levels to unlabelled form fields.

    Feature
  2. 02

    Broken link checking

    Frank tests every internal and external link on every page, follows redirects, and flags 404s, server errors and dead development links.

    Feature
  3. 03

    Figma design QA

    Map your Figma pages to your live site once, then review every page side by side with its approved design.

    Feature
  4. 04

    For Framer

    Automated QA for Framer sites: check every page and CMS page on your staging or preview URL before you publish to your domain.

    Solution
  5. 05

    For Webflow

    Automated QA for Webflow sites: check every page and CMS template on your webflow.io staging site before you connect the domain.

    Solution
  6. 06

    For WordPress

    Automated QA for WordPress sites: check every page on your staging site for lorem ipsum, broken links and accessibility before launch.

    Solution
  7. 07

    For agencies

    Consistent, automated QA across every project and every team member, with a scored record of every scan.

    Solution
  8. 08

    For freelancers

    A second pair of eyes for solo designers and developers: automated checks on every page, so you can hand over with confidence.

    Solution
  9. 09

    Frank vs BugHerd

    BugHerd collects visual feedback from clients and teams. Frank runs automated QA checks on every page. Here's how they compare.

    Comparison
  10. 10

    Frank vs Pixelay

    Pixelay overlays a Figma design on a live page inside Figma. Frank reviews every page against its design and runs automated QA checks too.

    Comparison
  11. 11

    Frank vs Sitepager

    Sitepager tracks what changes on a site between updates. Frank checks a build before launch and lines it up with the Figma design. Here's how they compare.

    Comparison
  12. 12

    Frank vs manual QA

    Manual QA is slow, inconsistent and easy to skip. Frank automates the repetitive half, so your team keeps the judgement calls.

    Comparison
  13. 13

    Lorem ipsum checker

    Frank checks every block of visible text on every page for Latin filler, in any word order, and flags it before your client sees it.

    Feature
  14. 14

    QA reports & scores

    Every page gets a score out of 100 and a red, amber or green status, with issues highlighted on a screenshot, every scan kept, and reports you can share with clients by link.

    Feature

Reading for QA teams

All articles

Give every issue an owner.

Run your first scan in minutes. Every plan includes unlimited projects and unlimited scans.

Get startedSee pricing
  • Set up in 30 seconds
  • Unlimited scans
  • No code required