Frequently asked questions

It lets teams run localized search checks with controlled country, language, and device context, then share those results without losing that context.

A VPN changes your IP, but it does not give you a repeatable workflow for device settings, clean sessions, result sharing, and team handoff.

The workflow generates real search result pages using the selected market context, rather than static mock screenshots.

Yes. Searches can be saved and shared as links so the recipient sees the same query context and output.

The platform supports checks across 195+ countries, with device and language controls available across the workflow.

No. PPC, content, localization, PR, product, and agency teams also use it for market-specific verification.

No. The workflow runs in the product, so there is no VPN setup or local browser configuration required.

Yes. Saved searches make it easier to compare markets and revisit previous checks with the original context preserved.

Yes. Starter lets you test the workflow and understand how localized checks work before committing to larger usage.

Paid plans unlock broader targeting and more workflow control, including city-level checks on higher tiers.

Yes. Teams can move to a higher plan when they need more projects, tokens, sharing, or multi-user support.

No. Monthly allocations are designed for recurring workflows, while one-time top-ups cover temporary volume spikes.

API access is available on higher plans for teams that want to automate search checks and reporting workflows.

Yes. If your team needs onboarding help, larger token volume, or a custom setup, contact us.

The Privacy Policy lists account data such as name, email address, hashed password, workspace or organization details, and role.

Search and usage data can include the queries you run, selected location, language, device, SafeSearch settings, result metadata, saved searches, projects, tracked keywords, and API usage.

Shared results preserve the query context and output so teammates or clients can review the same localized result instead of relying on disconnected screenshots.

The Privacy Policy allows product analytics and, where enabled, session recordings and heatmaps to improve the product. Input fields are masked in session recordings.

Yes. Subject to applicable law, you can request access, correction, erasure, restriction, objection, portability, or consent withdrawal by contacting privacy@isearchfrom.com.

Use privacy@isearchfrom.com for access, correction, deletion, portability, or other privacy questions. Product and billing questions can go to info@isearchfrom.com.

iSearchFrom is operated by Pakaje, UAB, a company registered in Lithuania at J. Basanavičiaus g. 26, Vilnius, Lithuania, VAT LT100019481311.

The Privacy Policy states that Pakaje, UAB acts as data controller and processes personal data in accordance with the GDPR and applicable Lithuanian law. It also documents data categories, legal bases, rights, retention, transfers, and processor categories.

No. The Privacy Policy says full payment card details are handled directly by the payment processor and are not stored on iSearchFrom systems.

MCP connections are bound to one workspace. The implementation uses OAuth consent, consent-time permission grants, live role checks, and a read-only query path that binds queries to the caller's organization.

No public SOC 2, ISO 27001, or similar certification report is currently published. The Trust Center lists what is published today and what should not be claimed until it exists.

A public status page or contractual uptime SLA is not currently published on the landing site. If uptime or incident-process details matter for your review, contact support with the requirement.

Teams running international SEO, PPC QA, localization reviews, and client reporting typically see the most value.

Yes. Device context is part of the workflow, so teams can compare how results shift across devices.

Yes. Shared result links help agencies support recommendations with context that clients can review directly.

Yes. Teams use it to validate ads, rankings, and localization before campaigns, releases, or market rollouts.

It helps teams see whether AI answers mention their brand, how competitors appear, and how recommendation patterns change over time.

The workflow is designed around major AI answer surfaces such as ChatGPT, Gemini, Perplexity, and AI-enabled search experiences.

Teams can run checks on demand today and use recurring workflows as the monitoring product expands.

Yes. Competitive comparison is a core part of understanding share of voice and recommendation patterns across prompts.

Yes. Geo context matters for both search and AI answer surfaces, especially for brands operating across multiple markets.

It is designed to reproduce market context more reliably than ad hoc VPN checks by controlling location, language, and device settings together.

Yes. Higher-tier workflows support city-specific targeting when your team needs more precise local validation.

Yes. Teams can review how results differ across mobile, desktop, and tablet contexts.

Yes. Safe search can influence the returned result set, so it is included as a controllable part of the workflow.

Yes. Teams can keep results as links and use export-ready workflows on higher plans.

It monitors exactly where your keywords rank in Google search results over time, from the locations, languages, and devices your audience actually uses.

You can trigger a check on demand at any time, or schedule automated daily and weekly checks so positions update without manual work.

Yes. Add competitor domains to any campaign and see who ranks for each keyword, so you can benchmark your visibility against theirs side by side.

Very much. Google returns different results by country, language, and device, so every check runs from the exact location and device profile you choose across 195+ countries.

Yes. Positions come from real, live Google searches run through localized infrastructure, not modeled estimates or cached data.

It monitors which advertisers run Google Ads on your keywords over time, capturing their position, ad copy, and landing pages from the locations, languages, and devices your audience actually uses.

You can run a check on demand at any time, or schedule automated checks so new ads, paused ads, and new advertisers are captured without manual work.

Add the keywords you care about and the competitor domains you want to watch. We capture the paid results for each keyword, the advertiser, position, headline, description, and display URL.

Significantly. Advertisers target by country, language, and device, so every check runs from the exact location and device profile you choose across 195+ countries.

Yes. Ads come from real, live Google searches run through localized infrastructure, not modeled estimates or cached data.

Model Context Protocol is the open standard AI assistants use to call external tools. Connecting iSearchFrom over MCP means Claude, Cursor, ChatGPT and other agents can run searches, manage campaigns and query results for you, instead of you copy-pasting between tabs.

Any MCP client that supports remote servers: Claude (web, desktop and Claude Code), Cursor, Windsurf, ChatGPT (with developer mode enabled), VS Code and more. If your tool speaks MCP, it can connect.

The MCP server is included in the Team plan. It's separate from API access, and unlike the API there's nothing to code: you connect straight from your AI app's settings.

There's no separate metering. Tool calls spend the same token balance as the app: a proxy search costs one token per page, tracker runs one token per keyword or check. All reads (results, analytics, SQL) are free.

Only if you let it. Write and delete capabilities are individual checkboxes on the consent screen. Grant read-only access and the agent can look but never touch.

Every connection is bound to one workspace. Row-level security pins queries to that workspace at the database layer, the SQL tool runs on a read-only role with column-level grants, and system tables are unreachable.

Revoke the connection at any time. The token dies immediately. Role downgrades propagate too, since permissions are re-checked live on every call.

Grids run from a single point up to 13×13, with a radius from 250 m to 50 km. A run costs one token per grid point per keyword, plus one token per keyword for the local pack, and the campaign form shows the exact number before you save. Switched-off points cost nothing.

A rank-weighted visibility score across the grid, from 0 to 100. Rank 1 at every active point is 100. Points you switched off, and points that could not be read, are left out rather than counted as misses.

Because they rank differently. The local pack is the three-result box on the normal results page; the map canvas is what people scroll on Google Maps. A business can be first in one and absent from the other, and the campaign shows both for the same keyword.

A hollow pin is a point that could not be read after retrying on a second provider. It is shown as unchecked rather than scored as a miss, it is excluded from every figure, and the tokens for it are refunded. A grey pin is different: the search worked and you were not in the results.

Yes. Every run has a public report link with the grid, the scores, the competitors and the trend, plus CSV and PDF export. Anyone outside your organization sees the report without owner details.

Maps Visibility is included in Pro and Team. Every workspace can open the tool and explore a read-only sample campaign before upgrading. It is in beta: the grid, the scores and the report are live, and we are still tuning the edges.

Only your organization's: position tracker, ad tracker, AI visibility and Maps campaigns with their runs and results, plus your proxy and direct search history and projects. It cannot see other customers, billing, or anything outside those tables.

No. Every query runs through a read-only database role inside a read-only transaction, and only single SELECT statements are accepted. Writes, schema changes and system tables are refused before they reach the database.

It says so. If the tables cannot answer a question, the reply explains what is missing instead of inventing a number. Every answer shows the SQL and rows it used, so you can check it yourself.

A few tokens from your organization's balance, charged per answer and shown under it. The charge follows the actual work: a short follow-up in an existing thread costs less than a cold question that needs several queries.

Not unless you share them. Threads are private by default; you can open one to the whole organization, and you can rename or delete your own at any time.

It is in beta. The questions it handles well are the ones on this page, and it will get better at the rest as we read the feedback on answers. The rules around your data are not beta: reads are read-only and scoped to your organization, and you only pay for answers you receive.