Inputs to change
- Nodes `probe`, `audit`, and `page`: point all three to the launch URL.
- Node `report`: change the filename and title for the launch.
Check a launch URL's HTTP response, technical page signals, and bounded readable copy, then preserve the evidence in one report before a campaign goes live.
Updated 1 August 2026 from the executable catalog.
Node labels and costs come from the registry. Dependency captions come from each node's dependsOn field, including parallel starts and approval gates.
web_check_url_statusweb_audit_pageweb_fetch_pagereport_renderThe following notes are shipped beside the executable definition.
Every operation below is present in this template's JSON and has no private rollout gate in the registry.
Fetch a URL and report its HTTP status, whether it redirected, and the final URL. Useful for monitoring site and landing-page health.
web_check_url_statusRun an on-page audit of a URL covering technical SEO (title, meta description, canonical, indexability, H1s, viewport, language, alt coverage, content length, Open Graph), CRO (call-to-action presence, form friction, script/page weight), and AI visibility (JSON-LD structured data, section-heading structure). Returns a 0–100 score with graded findings. Compose with web_get_sitemap + a loop to audit a whole site.
web_audit_pageDownload a web page and return its title and readable text content (HTML stripped, capped). Use for reading landing pages, articles, or competitor copy.
web_fetch_pageCompose text, KPI metrics, inline charts, and tables (typically templated from upstream operation outputs) into a branded, self-contained HTML report stored as a workspace file. Supports white-label brand name/colour/logo. Returns the file id and download path; prints cleanly to PDF.
report_renderStart free to build workflows manually. This template's requirement panel shows what must be unlocked before execution.