Product

How VeriFalcon works

The workflow is intentionally simple: choose the right crawler mode, run a scan against the routes that matter, then review the results by failure type instead of parsing a raw crawl dump.

Use the JavaScript crawler for React, Next.js, SPA, and authenticated flows, or the static crawler for docs, blogs, and HTML-first websites where speed matters more than browser execution.

Start a JavaScript scan Read the category page

create a scan with or without authentication

crawl pages and discovered links with the right crawler mode

classify failures into actionable buckets

export reports or inspect results directly in the app

Proof

What The Workflow Includes Today

Two crawl modes

Use the JavaScript crawler for React, Next.js, SPA, and authenticated flows, or the static crawler for docs, blogs, and HTML-first websites where speed matters more than browser execution.

Live and post-scan reporting

The product already includes live scan updates plus post-scan tabs and exports for broken pages, resources, protected routes, JS errors, API failures, scanner errors, and grouped links.

Operational safeguards

The JavaScript path runs through browser lifecycle controls and queue management because the product is designed to be usable in real operations, not just in a demo crawl.

Screens

Workflow Screens From The Current Product

VeriFalcon JavaScript scan workflow — **Scan setup**The workflow starts with a real scan-entry route that already supports crawl scope, robots controls, and optional authentication.Open full image

VeriFalcon static scan results page — **Categorized report review**The scan ends in a results surface organized by issue type, which is exactly what this page is describing.Open full image

Step 1: choose the crawler mode

Use the JavaScript crawler for React, Next.js, Vue, SPA, and authenticated product surfaces. Use the static crawler for docs, blogs, and other non-JavaScript sites where raw HTTP crawling is enough.

That distinction matters because it changes both the coverage model and the types of failures that can be detected during the scan.

Step 2: crawl and classify

As the scan runs, VeriFalcon tracks broken pages, soft 404s, protected routes, blocked pages, JS failures, API failures, scanner errors, and discovered-but-not-crawled pages. The point is to separate failure classes that teams fix differently instead of burying everything inside one status bucket.

Step 3: review by issue type

Instead of making teams parse one giant blob of results, VeriFalcon exposes tabs and exports for the issue classes people usually fix differently.

That makes the workflow useful for engineering, QA, docs, and technical SEO teams without pretending all of them need the same report shape.

Explore

Continue with pages that map to adjacent use cases and comparisons.

JavaScript Site Crawler

See when to use the browser-driven mode.

Authenticated Website Crawler

See how login-aware scans fit into the workflow.