Scrapeer
Browser action

Go To URL Block

Go To URL navigates the browser to a page. It is usually the first browser action after Start and creates page context for Blocks that need an open page.

At a glance

Best for
Opening pages
Required setting
URL
Variables
URL accepts {{variableName}}
Error handle
Yes

What it does

Go To URL tells Scrapeer which page the browser should visit. Later Blocks such as Click Element, Extract Text, and Extract Data operate on the page opened by this Block.

The URL field can use variables, so a Flow can open a static page or a page assembled from earlier values.

Use it when

  • Open the first page in a Flow after Start.
  • Navigate to a page whose URL comes from a variable.
  • Refresh browser context before extracting or clicking.

Do not use it when

  • You need to go back in browser history; use Go Back.
  • You already have the correct page open and only need to wait for content.
  • You need to click a link on the current page; use Click Element.

Settings

The URL setting is required. Scrapeer interpolates variables before navigation, can wait for a selector, and stores the final URL after redirects.

URL

Required: Yes
Variables
Yes
Description
The page to open. The runtime normalizes common bare-domain input before navigating.

Wait for element

Required: No
Variables
Selector accepts variables
Description
Optional UI section for waiting until a selector is present after navigation.

Output variable

Required: No
Variables
Variable name
Description
Stores the final page URL after navigation. The default name is pageUrl.

Timeout

Required: No
Variables
No
Description
Maximum navigation time and, when enabled, element wait time in milliseconds.

Outputs

Go To URL exposes the current page URL for later Blocks and records navigation result details in the run output.

pageUrlstring

The final page URL after redirects, stored under the configured output variable name.

urlstring

The final URL reported by the runtime after navigation.

titlestring

The page title returned by the browser runtime after the page opens.

Example Flow

Use Go To URL early in a Flow so every page-dependent Block has a browser page to work with.

  1. Start the Flow.
  2. Use Go To URL with a fixed URL or {{variableName}} URL.
  3. Run extraction or interaction Blocks against the opened page.

Errors and fixes

Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.

The page does not open.

Check
Check that the URL field is not empty and that any variables resolve to a valid URL.
Fix
Use a full URL or a valid variable value before running the Flow again.

Later Blocks act on the wrong page.

Check
Inspect the Go To URL output and verify the final URL.
Fix
Update the URL or add a wait step before the next Block.

Local and cloud runs

Both local and cloud runtimes interpolate the URL and optional wait selector, wait when configured, and store the final page URL after redirects.

Cloud navigation also applies cloud-side browser safety checks before opening the page. Local run output can include status code details from Electron.

Wait For Element Block

Wait for page content after navigation.

Blocks

Understand how Blocks connect and pass state through a Flow.

Variables

Use saved values with the canonical {{variableName}} syntax.