VeriFalcon
Start scan
Route-integrity QA for launches

Find what breaks after the page actually loads.

VeriFalcon crawls public pages, JavaScript-rendered routes, and optional authenticated surfaces, then turns broken links, soft 404s, JS errors, API failures, and protected routes into a fix list your release team can use.

Static scan starts fastBrowser mode sees hydrationReports separate risk from noise
Start a fast scanUse browser modeMigration QA audit
Example scan outputapp.example.com
128 routes checked7 broken pages3 JS/API failures11 protected routes
Current product scope

One crawler family, three practical jobs.

The product is not pretending to be a mature monitoring suite or an AI auditor. It is a focused route-integrity tool for launch checks, migrations, and app QA.

HTTPStatic scanFast route and link sweepUse this for documentation, blogs, WordPress, marketing pages, and static HTML. It follows links quickly and flags broken pages, resources, soft 404s, and uncrawled routes.Up to 500 pagesNo browser sessionBest first passJSBrowser scanRendered application crawlUse this when routes appear after hydration, navigation depends on client-side routing, or failures only show up in the browser console or network layer.React / Next / VueOptional login setupJS and API failuresQAMigration auditPre-launch release checkUse this before redesigns, CMS moves, URL restructures, and client handoffs where missed routes become launch risk.Route integrityExportable evidenceLaunch triage
What the report separates

Not every non-200 response means the same thing.

VeriFalcon keeps fix work sorted by cause. A protected billing page should not sit in the same bucket as a removed pricing route, and a JavaScript crash should not be hidden behind a generic broken-link count.

7 categories shown2 crawler modesCSV/PDF handoff
StatusRouteSignalMeaning
OK/docs/getting-started200Rendered and reachable
BROKEN/pricing/legacy-plan404Fix redirect or remove link
SOFT404/guides/old-importer200Looks missing despite HTTP 200
JS/dashboard/importconsoleRuntime error after load
API/api/projects/42500Network failure seen by browser
AUTH/admin/billing403Protected route, not a broken page
TIMEOUT/reports/month-end30sSlow or blocked scan path
Full context

What this tool can do today.

Honest scope matters. These are the capabilities currently reflected in the product experience and backend scan model.

Discovery

  • Follow internal links
  • Separate crawled and uncrawled URLs
  • Respect robots.txt when selected

Classification

  • Broken pages and resources
  • Soft 404s that return HTTP 200
  • Protected, blocked, timeout, and scanner-error states

Browser evidence

  • JavaScript console errors
  • API failures from rendered pages
  • Authenticated flows when login setup is provided

Handoff

  • Live scan status
  • CSV exports
  • PDF report behind email capture
  • Email the result link when finished
Migration QA

Use it before the redirect map becomes a production incident.

Check old URLs, new routes, protected areas, docs, assets, and app flows before a redesign, CMS migration, or launch handoff.

Plan a migration audit
Developer QA

When browser behavior matters

Browser scans are for SPAs, authenticated flows, and pages where console or network failures reveal what HTTP-only crawlers miss.

Open browser scan
Technical SEO

When coverage speed matters

Static scans are the clean first pass for docs, blogs, public marketing pages, sitemap audits, and large HTML-first surfaces.

Open static scan
Need the operational details?

Review pricing posture, crawl safety, or the product background before a pilot.