Connect the AEO Toolkit to your AI client

Crawl a URL, parse its HTML and structured data, and score it for answer-engine optimization with prioritized fixes.

Query Perplexity Sonar with a prompt and check whether the URL is cited as a source, and at what rank (BYOK).

Generate realistic user prompts a site should aim to be cited for on a topic, optionally live-testing a few (BYOK).

Combine an AEO audit with per-prompt visibility checks into one report with an overall citation rate (BYOK).

Run one Perplexity Sonar query and rank several competitor URLs by whether and where each is cited (BYOK).

Find guest-post, resource-page, and roundup link prospects for a topic via classic outreach footprints, merged by host.

Find linked and unlinked mentions of a brand across the web, flagging unlinked ones as backlink opportunities.

Fetch a page and extract contact emails (including de-obfuscated and mailto) plus social media handles.

Return a Wayback Machine timeline for a URL: snapshot count, first/last archived dates, and direct archive links.

Draft a short, personalized cold outreach email (subject + body) from a contact and context, using your own LLM key (BYOK).

Fetch a page and confirm whether it links to a target domain, reporting anchor text, rel attributes, and dofollow status.

Approximate the pages linking to a competitor using free DuckDuckGo signals: a directional prospecting starting point.

List the Google Analytics 4 properties the connected account can access (propertyId + displayName).

List the Google Search Console properties the connected account can access (siteUrl + permission level).

Run a GA4 report for a property over date ranges with chosen dimensions and metrics, returning named rows.

Query Search Console Search Analytics over a date range, optionally broken down by query, page, country, device, or date.

Return the top search queries for a site over the last N days, ranked by clicks (with impressions, CTR, position).

Surface high-impression, low-CTR queries over the last N days: prime targets for title and meta rewrites.

Compare aggregate Search Console performance between two date ranges, returning per-metric absolute and relative deltas.

Explain why traffic changed between two periods: attributes the click change to individual pages or queries and ranks them by how much of the move each accounts for, reporting gains and losses separately.

Find queries two or more of the site's own pages compete for, and name the best-ranking page as the consolidation target.

Catch pages bleeding clicks before they fall off page one, flagging whether each also lost rank: which separates a competitor problem from seasonality.

Check whether Google has indexed up to 25 URLs per call (verdict, coverage state, last crawl, canonicals). Read-only; it cannot request indexing.

List the Bing Webmaster Tools sites the connected API key can access.

Bing's daily clicks and impressions series for a site, with totals across the series.

The top search queries for a site on Bing, ranked by clicks.

The top pages for a site on Bing, ranked by clicks.

The query-to-page pairing on Bing: which pages served a query, or which queries a page served.

Bing's crawl stats, crawl issues, and URL submission quota for a site: is Bing crawling and indexing it.

Keyword impression and broad-match volume around a seed term, from Bing Webmaster. Google Search Console exposes no equivalent data at all: this tool is Bing-only.

Query rows from Search Console and Bing Webmaster for the same site, merged by query with an explicit coverage block. Only the Google side honours the requested date range: Bing has no date-range parameter, so its rows are its own unwindowed aggregate.

Split a date range in half and classify each query by how it moved on each engine: held on Bing but dropped on Google (a Google ranking problem), dropped on both (a content problem), Bing-specific, or insufficient data. Both engines honour the range here: Google is queried per half, and Bing's undated rows are bucketed locally by each row's own date. An engine that could not answer yields insufficient_data, never a zero.