Rapid Indexer

Submit URLs and backlinks to Rapid Indexer for search engine indexing and check whether they made it in. Agents confirm new pages were actually indexed rather than assuming it.

4 actions API key available

Rapid Indexer website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

A batch of pages goes live, or a link-building run reports new placements

Agent collects the candidate URLs and fetches each one as a crawler would see it

Agent drops staging hosts, noindex directives, mismatched canonicals and empty stubs

Agent reads Get User Profile to confirm the credit balance covers the surviving batch

Agent prices the batch with and without the VIP queue, which consumes extra credits

SEO owner receives the accepted list, the rejected list with reasons, and both costs

SEO owner confirms the pages are actually finished before Create Indexing Task submits them

What This Integration Enables

Indexing is the step in the pipeline everyone assumes and almost nobody verifies. A page is published, a backlink is placed, a report says done, and the question of whether a search engine ever actually took the URL goes unasked until traffic fails to appear months later. Rapid Indexer answers that question directly, and this connector wires it into the flow that publishes the page rather than a monthly audit. Create Indexing Task submits a batch of URLs, either to push them for indexing or to check whether they are already indexed. Get Task Details returns the headline progress. Get Task Links returns the part that matters for reporting: each submitted URL with its status and the timestamp it was last checked, which turns "we published forty pages" into forty rows with outcomes.

One thing to know about scope. The same vendor endpoint also sells click-through-rate manipulation and synthetic-traffic campaigns. Those fabricate search and analytics signals, so they are deliberately not wired into this connector and no agent running on FlowRunner can reach them through it. The indexing and account endpoints are what is exposed. A second thing worth designing around: there is no endpoint that lists tasks, so a task ID that a flow fails to persist cannot be recovered. Write it to the record that started the batch before you poll it. Both of these are the kind of judgment a connector should carry so the flow above it does not have to.

Without FlowRunner

Indexing assumed, never verified Pages are published and everyone moves on, with no record of whether search engines took them

Backlinks reported as delivered A link-building run is closed out on the placement report, not on whether the linking pages are indexed

Submissions sent unchecked Whatever URL was in the spreadsheet gets pushed, including staging hosts and unfinished drafts

With FlowRunner

Indexing status recorded per URL Get Task Links returns a row-level outcome for every submitted page and the timestamp it was checked

Link runs closed on evidence Placements are only counted as delivered once the linking page shows as indexed

Batch screened before submission Each URL is fetched and checked against its own directives before a single credit is spent

Use Case Scenarios

Submission Gated on the Page Being Finished

A content batch publishes in WordPress. Rather than pushing the permalinks straight through, the agent fetches each new URL and reads what a crawler would: the canonical tag, the robots directive, the rendered title, and whether the body has real content or a placeholder the author left in. Pages that are noindex, canonicalized elsewhere, or thin get separated out with the reason attached. The agent reads Get User Profile for the credit balance, prices the surviving batch against the standard and VIP queues, and puts the two lists in front of the SEO owner before Create Indexing Task runs.

A Link-Building Run Closed Out on Evidence

A campaign reports twelve new placements. The agent submits the twelve linking pages, not the target pages, with Create Indexing Task, polls Get Task Details until the batch finishes, then reads Get Task Links for the per-URL outcome. Nine come back indexed and three do not. The agent writes all twelve rows to the campaign sheet in Google Sheets with their status and check timestamp, and flags the three as automation exceptions for the campaign owner. A link on a page no search engine has indexed is not yet a link, and the report now says so.

Auditing an Old Sitemap for Pages That Never Made It

A team suspects a chunk of the site was never indexed. The agent reads the sitemap, batches the URLs through Create Indexing Task in check mode rather than push mode, and collects the per-URL results from Get Task Links. The output splits the site into indexed and not indexed, which is the input to a real decision: which sections deserve internal links, which pages should be consolidated, and which should be left alone. The agent produces the map; the SEO lead decides what to do with the parts of the site search engines never took.

Human-in-Loop Highlight

Submitting a URL for indexing is an invitation. You are asking a search engine to come and look now, and what it finds is the version it takes away. Push a page that still has a placeholder heading, a canonical pointing at a competitor's template, or a staging hostname that leaked into the permalink, and the fix is not an undo. It is a second crawl you also pay for, on a schedule you do not control. So the gate sits in front of Create Indexing Task and carries the evidence: "Batch of [N] URLs ready to submit. [N] accepted, [N] held back: [URL] is noindex, [URL] canonicalizes to [other URL], [URL] returned under 200 words. Credit balance [amount], standard queue costs [amount], VIP queue costs [amount] more. Confirm these pages are finished, or send the held-back list to the writers first?" The agent did the crawl-eye check and the arithmetic. A person confirms the pages are ready to be seen.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

4 actions

Account

Get User Profile Returns the connected account's ID, email, sign-up date and remaining credit balance. Used as the guard before pushing a large batch, since every URL consumes credits and a task fails outright once the balance runs dry, and as a connection test for a newly configured key.

Indexing

Create Indexing Task Submits a batch of URLs either to push them for indexing or to check whether a search engine has already indexed them, returning the task ID to poll. Used at the end of a publishing or link-building flow, with a recognizable title so the batch can be identified later and the VIP queue reserved for batches that genuinely need to jump the line.
Get Task Details Returns a task's title, type and status with a breakdown of how many URLs have been processed and how many remain. Used as the polling step after submission, since indexing runs asynchronously and a batch can take hours to finish.
Get Task Links Returns the per-URL outcome for a task: each submitted link with its indexing status and the timestamp it was last checked. Used for reporting, because this is the call that turns a finished task into a row-level record of which specific pages made the index and which did not.

Frequently Asked Questions

What can FlowRunner do with Rapid Indexer?

FlowRunner agents can run Get User Profile, Create Indexing Task, and Get Task Details in Rapid Indexer, plus 1 more action.

Does connecting Rapid Indexer to FlowRunner require OAuth?

No. Rapid Indexer connects to FlowRunner with an API key, no OAuth flow required.

Can Rapid Indexer trigger a FlowRunner workflow automatically?

Rapid Indexer doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Rapid Indexer

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us