FAQ

How does change detection work?

Site Spy takes snapshots of your watched pages at the interval you set (from minutes to weekly). When changes are detected, a visual diff highlights exactly what changed — green for additions, red for removals. You can browse the full snapshot timeline to compare any two versions.

Is Site Spy free?

Yes. The free plan lets you track up to 5 websites with hourly checks. For more watches and faster check intervals (down to 1 minute), upgrade to the Starter or Pro plan.

Which browsers are supported?

Chrome and Firefox are fully supported. Safari support is coming soon.

When signed in, your watches sync across browsers automatically.

Can I track specific parts of a page?

Yes. The element inspector lets you click any element on a page to monitor just that section. This is useful for tracking prices, stock status, specific headlines, or any other page element — while ignoring dynamic content like ads or timestamps.

What is the MCP integration?

Site Spy provides an MCP server that integrates with AI assistants like Claude, Cursor, and other MCP-compatible tools. Your AI assistant can monitor websites, compare snapshots, and summarize changes through Site Spy.

To set it up, copy your API key from the dashboard and add the MCP server configuration to your AI client's settings file.

What happens if I lose my API key?

If you're signed in with an account, you can regenerate your API key from the dashboard or extension settings. Your watches are tied to your account and will be migrated to the new key.

If you're using anonymous mode (no account), losing the key means losing access to your watches. We recommend creating an account to avoid this.

How do I get faster notifications?

Upgrade to the Starter plan for check intervals as low as 10 minutes, or the Pro plan for intervals down to 1 minute. You can also set up email and Telegram notifications for multiple alert channels.

Does Site Spy work on all websites?

Site Spy works on most publicly accessible websites. It cannot monitor:

• Pages that require authentication (login-protected content)
• Browser internal pages (chrome://, about:)
• Content loaded only via JavaScript interactions (e.g., infinite scroll)

The server handles content checking, so it sees what a fresh page load would show.