RankRoot: AI visibility audit

Turn one page (url) or text into a native post for every enabled channel in every chosen language, saved as drafts. Nothing is published. Use dry_run to see posts without saving, and idempotency_key so a retry never makes a duplicate. Needs the customer's key.

Change a draft's text, thread or title. The platform checks (length, hashtags, hype words, required settings) run again and come back as warnings.

Posts newest first, with status (draft, scheduled, published, failed, rejected), schedule time, live URL, warnings, claims to confirm and engagement metrics.

Write native posts for X, LinkedIn and Threads from any public page, in up to 3 languages, so the user can see what RankRoot Amplify would publish. Free, no key. Nothing is stored or posted.

Schedule draft posts in the customer's Postiz at the next good local time for each platform and language (or at `at`), within the per-channel daily cap and spacing. Only works if the customer allowed agents to schedule; posts with claims to confirm or warnings are skipped for the owner to review. Returns what was scheduled and why anything was skipped.

Connected channels, languages, mode, guardrails, post counts and what has performed best for this customer. Needs the customer's AI Visibility Employee key.

Score how discoverable a website is by AI answer engines (ChatGPT, Perplexity, Claude, Google AI Overviews) and AI agents. Returns a 0-100 score, per-category scores and a prioritized fix list.

Classic SEO audit of a page, weighted like a full SEO audit: technical (canonical, indexability, redirects, HTTPS/HSTS, security headers, mobile viewport, hreflang, 2 MB HTML limit, back-button hijacking), content and E-E-A-T trust signals, on-page (title, meta description, headings, internal links, anchor text), schema validation (parse errors, required properties, retired rich-result types), performance, images and AI search readiness. Returns a 0-100 score and prioritized issues with fixes.

Check which AI crawlers (OAI-SearchBot, ChatGPT-User, GPTBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended and more) a site's robots.txt and firewall/CDN let in. Flags blocked AI search bots, which cost citations.

LCP, INP and CLS for a URL from Google PageSpeed Insights (mobile): Chrome UX Report field data (75th percentile, 28 days) when Google has it, plus Lighthouse lab metrics and the biggest speed opportunities. Takes up to a minute.

Generate ready-to-publish llms.txt, an AI-bot-friendly robots.txt and schema.org JSON-LD for a website, based on its current homepage.

Get the Polar checkout link for one RankRoot plan, to hand to the user. The user pays on Polar and receives a license key by email; pass it as 'Authorization: Bearer <key>' for higher API/MCP limits. If checkoutOpen is false, the link is an application form the user fills in instead.

List RankRoot plans (free scan, Traffic Boost one-time, done-for-you AI Visibility Employee monthly) with prices, limits, checkout links and which plan fits which user. Agents with a USDC wallet can pay directly over x402: GET https://getrankroot.com/api/agent/check?url= ($0.50) or POST https://getrankroot.com/api/agent/employee {website} ($149, 30 days, key returned at once). Otherwise give the user the checkout link.

Find software products for a need: new SaaS, AI tools and apps launched on RankRoot, each with a fact-checked profile (what it does, who it's for, pricing when published). Pass the user's need as query ("invoicing for freelancers", "uptime monitoring"). Featured products are paid placements and are marked. Optional category: an industry slug such as sales-crm or product-analytics.

Launch the user's product on RankRoot for free: a public launch page, a listing in the launch directory and the product's category, and a count of visitors sent. Free launches go live in about a week after the user confirms by email. With a Traffic Boost license key (key) it goes live today and is featured for 30 days. Ask the user before submitting: it publishes their product publicly.

Fetch a site's llms.txt (pass the site URL, or a URL ending in /llms.txt or /llms-full.txt for a subpath file) and check it against the llmstxt.org format: H1, summary, H2 link lists, Optional section.