Cookbooks

Guides explain one feature. Cookbooks solve a whole task — they stitch several features together into a complete, working recipe you can follow start to finish. Every recipe states its goal, what you need, the exact steps, runnable code where relevant, and how to verify it worked.

Each recipe is self-contained. Pick the one that matches what you’re trying to do:

Track rankings across countriesMonitor the same keywords from several countries on a schedule, and read the movements.

Automate SERP monitoring with the APIA complete script that runs localized searches and exports the results on a cadence.

Send alerts to SlackWire campaign alerts to a Slack channel with an incoming-webhook relay.

How recipes are structured

Every cookbook follows the same shape so you can scan or follow along:

1. Goal — what you’ll have when you’re done.
2. You’ll need — accounts, features, permissions, and tools.
3. Steps — numbered, with UI paths or runnable code.
4. Verify — how to confirm it works.
5. Variations — common tweaks and where to go deeper.

Two ways to do most things

Almost every recipe can be done in the app (point-and-click) or via the API / MCP (automation). Recipes show whichever fits the task, and link to the reference when you want the full surface:

In the app

Best for one-off and interactive work. No code. Everything in the recipes maps to a screen in app.isearchfrom.com.

With the API or MCP

Best for scheduled jobs, pipelines, and AI agents. See the API Overview and the MCP Server.