Content Node
A single element in Chrome's page representation. Each node carries a type (one of 21, from headings and links to form controls and dialogs), bounding box coordinates, text styling, accessibility metadata, and an ID that the AI uses to reference or interact with that specific element.
When Google Chrome prepares a web page for the Gemini artificial intelligence, it translates the page's visual layout into a structured hierarchical tree. Every visible element on the page becomes a single content node.
Chrome assigns each node one of twenty-one distinct types. These types tell the AI how to interact with the element. For example, a heading signals the structure of the document, an anchor is something the AI can click, and a form control is an input it can fill out.
But these nodes carry more than just a type. They also contain precise geometric data, including the element's outer and visible boundaries in screen pixels. They hold text styling details like font size and color, along with crucial accessibility metadata, such as whether an element is focusable or disabled.
To keep things efficient, Chrome filters out the background noise. It strips away structural containers and layout wrappers that don't add meaning. On a typical webpage, Chrome might look at nearly five hundred nodes in the rendering tree, but it will only pass about two hundred of those tagged nodes to Gemini. This distilled, structured format gives the AI exactly what it needs to read, understand, and navigate the web just like a human would.
A single element in Chrome's structured page representation. When Chrome extracts a page for Gemini, every visible element becomes a content node in a hierarchical tree.
Each node is assigned one of 21 types: Root, Container, Text, Paragraph, Heading, Anchor, Image, SvgRoot, Canvas, Video, Form, FormControl, Table, TableRow, TableCell, OrderedList, UnorderedList, ListItem, Iframe, DialogModal, and DialogModeless. The type determines how the element is treated — a FormControl is something the AI can fill in, an Anchor is something it can click, a Heading signals document structure.
Beyond type, each node carries geometry data — three kinds of bounding box (outer, visible, and fragment) in viewport pixel coordinates — text styling (font size ratio, emphasis, color), accessibility metadata (focusable, tabbable, disabled, 16 possible clickability reasons), and landmark roles (header, nav, main, footer, etc.).
Not every node in the full rendering tree reaches Gemini. Structural containers and layout wrappers are filtered out. For a typical page, Chrome might extract 471 nodes from the rendering tree but only pass 198 tagged nodes in the structured Markdown — the ones Gemini can read or interact with.