Page Types Reference

browsy classifies every page into a PageType to help agents decide what to do next. The classification is based on structural heuristics applied to the Spatial DOM -- no machine learning, no external services.

Page types are evaluated in priority order. The first match wins.

PageType enum

#![allow(unused)]
fn main() {
pub enum PageType {
    Error,
    Captcha,
    Login,
    TwoFactorAuth,
    OAuthConsent,
    Inbox,
    EmailBody,
    Dashboard,
    Article,
    SearchResults,
    List,
    Search,
    Form,
    Other,          // default
}
}

Detection criteria

Evaluation order

The order matters. For example:

• A login page with a search bar in the nav is classified as Login (password field check comes first), not Search.
• A search results page with many links is SearchResults, not List, because SearchResults is checked before List.
• An article with a search bar is Article, not Search, because Article is checked first.
• An error page with a login form is Error, because error checks come before Login.

Accessing page type

Rust

#![allow(unused)]
fn main() {
use browsy_core::output::PageType;

let dom = browsy_core::parse(html, 1920.0, 1080.0);
match dom.page_type {
    PageType::Login => println!("This is a login page"),
    PageType::Article => println!("This is an article"),
    _ => println!("Page type: {:?}", dom.page_type),
}
}

Python

page = browser.goto("https://example.com")
print(page.page_type())  # "Login", "Article", "Other", etc.

MCP

The page_info tool returns page_type as a string. The browse tool includes it in the JSON output format.

JSON serialization

PageType is serialized as a string. The field is omitted from JSON when the value is Other (via skip_serializing_if).

{
  "page_type": "Login",
  "title": "Sign In",
  "url": "https://example.com/login"
}