OpenRush

Fast, opinionated technical / content health audit across a sampled set of a domain's pages, tuned for organic-search signal over noise. Discovers URLs from the sitemap/robots (or a homepage link-crawl fallback), then samples one representative per URL template BY VALUE: money/content pages first, while enumerated low-value sections (e.g. a jobs board or event listings) get a single spot-check rather than eating the budget. Fetches the sample concurrently, then GATES OUT non-indexable pages — anything intentionally `noindex` (on a low-value page) or canonicalized to another URL is excluded from scoring instead of being reported as a problem (a noindexed job listing is working as intended). Returns: grouped `issue_clusters` (issue + severity + affected page count + which page roles + a fix), a ranked `recommendations` list weighted by the *value* of the pages affected, an `onpage_score`, and cross-page duplicate-title/description checks. Full per-page rows — including excluded pages and why — are linked via `resources` (fetch with export_dataset). Runs in seconds. - `max_pages` (default 10, max 20): how many sampled pages to audit. Key fields: `page_class_summary` (sampled pages by role: core/content/ utility/ephemeral), `pages_excluded` + `excluded_summary` (non-indexable pages skipped, by reason), and `worst_page` (the highest-value page with the most issues — the best drill-down target). Each cluster/recommendation carries `page_classes` so you can tell whether a finding hits money pages or just utility ones. Scope: this reads each page's raw HTML — it does NOT execute JavaScript or measure Core Web Vitals. `render_warning: true` means ≥1 audited page looks client-rendered (its raw HTML is near-empty), so its content checks are low-confidence. Also read `coverage` (audited vs discovered), `discovery_source` (a `homepage_fallback` means no sitemap was found), and `fetch_failures` (pages that didn't respond in time). To confirm which findings hit pages that actually earn search traffic, follow the `inspect_domain` / `inspect_page` next_actions. Only audit a domain the user owns or operates. If ownership isn't already clear from the conversation, confirm with the user before calling this tool.

audit_site

Backlink gap analysis: referring domains that link to one or more competitors (1-10 domains) but NOT to `domain`. This is the link-building counterpart to compare_keyword_coverage — every row is a concrete outreach target, ranked by the referring domain's authority and how many competitors already earned the link (more = more relevant and reachable). Use after discover_competitors to turn a rival set into a prioritized link prospecting list. Backed by the cross-engine backlinks index (no location needed).

compare_backlink_gap

Keyword gap analysis: terms one or more competitors (1-10 domains) rank for that `domain` does not, plus terms where the target is losing ground. Use after discover_competitors to turn a competitor set into a concrete content/keyword target list. Results group into intent clusters so the agent can prioritize. Both target and competitors must be reasonably indexed for the gap set to be meaningful — see `coverage`.

compare_keyword_coverage

START HERE. List the live OpenRush surface: enabled data domains, the tools in each, the fact types every tool can emit, which sources back them (live SERP, search index, backlinks, owned Search Console/Analytics/Ads), and which tools need an owned-data connection. Use this to discover what's available before assuming a tool exists. Returns the standard OFE envelope; the tool list is in `data.tools`.

describe_capabilities

Find organic competitors. Provide exactly one of `domain` or `seed_keywords`. - domain mode: competitors by keyword overlap with the target's indexed set. Broad, but unreliable for new/small sites because the search index lags the live SERP — the response flags this with a `data_freshness` fact. - seed_keywords mode (1-20 queries): aggregates who consistently ranks across those queries by hitting the live SERP database directly. Works for any target including pre-launch. Prefer this when the domain is new or domain mode came back thin.

discover_competitors

Fetch the full rows behind a dataset `uri` that another tool returned in its `resources` block (results too large to inline). Pass the uri verbatim; do not construct one yourself. Datasets are retained for a limited window and may be dropped sooner under load, so a valid uri can come back empty. That is not an error: when it happens the response has `data.available = false` with a `note`, and `next_actions` contains the tool to re-run to regenerate the dataset. Follow that action, then export the fresh uri from the new `resources` block.

export_dataset

Measured Google Search performance (clicks, impressions, CTR, impression-weighted position) for one of the user's OWN websites, straight from their connected Search Console — not a modeled estimate. `website_id` and `domain` are optional, interchangeable selectors: omit both and the single connected website is auto-selected. If the account has several connected websites the call returns a `website_required` error listing safe options in `data.options` — retry with one `website_id`. If nothing is connected yet it returns `connection_required`/`binding_required` (set up in the dashboard). - `period`: last_7_days | last_28_days (default) | last_3_months | last_6_months | last_12_months | last_16_months - `compare_to`: previous_period (default) | previous_year | none - `group_by`: any of page | query | date | device | country (omit for the site total; page + query is allowed but bounded) - `search_type`: web (default) | image | video | news | discover The most recent ~3 days are labeled preliminary; GSC reports search performance, which is not the same as total website traffic.

get_search_performance

Measured website analytics (sessions, users, engaged sessions, engagement rate, average engagement time, page views, bounce rate) for one of the user's OWN websites, straight from their connected Google Analytics (GA4) property — not a modeled estimate. `website_id` and `domain` are optional, interchangeable selectors: omit both and the single connected website is auto-selected. If the account has several connected websites the call returns a `website_required` error listing safe options in `data.options` — retry with one `website_id`. If nothing is connected yet it returns `connection_required`/`binding_required` (set up in the dashboard). - `report`: overview (default, a rich summary: site totals + top channels + top landing pages + a daily trend) | channel | source_medium | campaign | landing_page | country | device | date - `group_by`: the lower-level equivalent of `report` (one dimension) - `period`: last_7_days | last_28_days (default) | last_3_months | last_6_months | last_12_months - `compare_to`: previous_period (default) | previous_year | none Windows are computed in the property's own reporting timezone. The most recent ~1-2 days are labeled preliminary. Sessions are visits, not users, and are not the same as Search Console clicks. This is the universal traffic/attribution/engagement tool: it deliberately reports NO conversions, revenue, or custom events.

get_website_analytics

Full backlink profile for one domain: a link-authority summary (domain_rank, referring domains, total backlinks, dofollow ratio, spam score), the top referring domains ranked by authority, and the anchor-text distribution. Use to judge how established/trustworthy a site is, or to understand the shape of its link profile before planning link building. Backed by the cross-engine backlinks index, this tool is independent of the organic search-index tools and works even when their coverage is thin. The `next_actions` point to compare_backlink_gap for outreach targets.

inspect_backlinks

Starting map for any domain: top organic keywords, top pages, estimated traffic, dominant search intents, and likely competitors in one call. Use this first when handed a bare domain. The `next_actions` typically point to inspect_page (for a winning URL), research_keywords (around a theme), or discover_competitors. Backed by the search index, so a brand-new or barely-indexed domain may return thin `data` — check `coverage` before concluding a site ranks for nothing.

inspect_domain