| Entry price | Starter, billed monthly ($490/yr paid annually) — 4 of 6 AI engines per run on your own keys, 20 tracked prompts per project, site check, SEO/GEO audit and the Evidence Engine on demand. | Base plan, per domain — 25 tracked prompts, 1 domain. Shown to us in GBP, the same on the monthly toggle; Semrush’s own help page gives $99 a month. Semrush localises pricing and we have not converted it. | Starter, billed monthly — 50 prompts, 3 active AI models at a time, 1 project. |
| Finds AI visibility gaps | YesThe Evidence Engine mines AI-visibility runs for topics where a competitor is named and you are not, then ranks them by impact. | YesThe AI Visibility Toolkit tracks whether ChatGPT, Google AI Overviews, Gemini and Perplexity mention or cite your brand against named competitors. | YesContent gap analysis surfaces topics where a competitor is visible in AI answers and you are not. |
| Can generate content | YesWriters draft the missing page from the business's own pages, videos and confirmed words only; nothing is invented to fill a gap. | YesThe Content Toolkit's AI Article Generator writes full articles, and its Content Optimizer rewrites and expands existing copy. | PartlyActions itself stops at analysis - asked if you still write the content yourself, its own FAQ says "Yes - and that's intentional." Connected to an agent such as Claude over MCP, Peec's own published use case has the agent draft the post. |
| Can publish content | YesWordPress, Shopify, Wix, Ghost or a signed webhook; nothing is reported published until the site hands back the live address. | YesThe Content Toolkit publishes a finished article straight to a connected WordPress site from its own editor. | YesIts content optimisation docs now carry a WordPress button: "If the article is linked to WordPress and publishing is available to your account, click Publish to WordPress." Its published MCP use cases also show a connected agent publishing straight to WordPress. |
| Automatically creates evidence for a specific measured gap | YesClosing a gap runs the same writer pipeline that drafts and publishes the missing page, then records what was produced against that gap. | Not statedContent Optimizer connects to your AI-visibility data to guide a rewrite, but nothing on the pages we read ties one measured gap to one generated asset automatically. | PartlyNot a native Peec workflow, but its own published use case chains Peec's gap data straight to an agent that drafts and publishes one piece per gap automatically. |
| Claims constrained to verified business-owned material | YesEvery rewrite is checked against the business's own pages, videos and words after it is written and before it is pushed live; anything unsupported holds the page for the owner instead of publishing it. | Not statedNot stated as an equivalent rule on the pages we read. | Not statedNot stated as an equivalent rule on the pages we read. |
| Publishes and ties the live URL back to the originating gap | YesClosing a gap records the live page's own address against that same gap the moment it publishes. | Not statedNot stated on the pages we read. | Not statedPeec's own auto-publish use case publishes through a connected agent, but nothing on their pages ties the resulting page back to the gap as a native record. |
| Re-runs the originating questions to test whether that gap closed | YesOn the questions you're measuring: closing a gap adds its topic to your AI-visibility watchlist, and your plan's cycle re-asks it and reports the change either way. | Not statedTracked prompts refresh on their own schedule, but nothing on the pages we read ties one re-check back to one content fix. | PartlyIts own MCP use cases can measure whether a campaign changed how AI describes your brand, but an equivalent loop tied to one specific fix is not clearly stated. |
| Confidence ranges & sample sizes | YesA run’s named, cited and recommended rates carry a 95% confidence range and their sample size; repeat sampling reports stability separately. | Not statedNot stated on the pages we read - though Semrush's own help centre agrees AI responses are personalised, saying "no platform can provide exact numbers on visibility": a caveat we'd echo. | Not statedEach metric is defined precisely on their methodology page, but without a confidence interval or sample size. |
| Tracked prompts, asked on a schedule | YesUp to 20 exact questions per project on every plan, asked on your own keys daily, weekly or monthly, every answer kept with whether you were named and what was cited. | Yes"Track 25 custom prompts (daily AI rankings)" on the Base plan, per domain. | Yes"50 prompts" on Starter, "Choose 3 models", 1 project. |
| Asks Google AI Mode your tracked prompts | YesYour tracked prompts asked of Google AI Mode itself through DataForSEO, from your project's location, on each prompt's own schedule — named and cited counted on their own line, on your own DataForSEO credit. | Yes"Track your domain's positions for target prompts in ChatGPT Search, Google's AI Mode, and Gemini." | Yes"AI Mode" is among Starter's available models, and its changelog of Aug 3, 2026 reads "AI Mode is now tracked in France, so French prompts return AI Mode results". |
| Asks the ChatGPT and Gemini apps themselves, not only the vendors' APIs | YesDataForSEO asks the ChatGPT app and the Gemini app through their own web pages, from your project's location, on your own DataForSEO credit; the answers are kept on their own line beside the API answers. | Partly"Prompt responses are captured from real requests and not via any APIs of LLMs" — said of its Prompt Database, not of Prompt Tracking, and no page we read names a consumer app or web interface. | Yes"Instead of APIs, Peec AI uses browser automation to interact with AI platforms through their web interfaces" — though its channel list still names some API channels, and Enterprise's extra models are each tagged "API". |
| Google AI Overviews measured as their own surface | YesWhether Google's AI Overview names or cites you for the searches you choose, read from a live Google results page from your project's place, kept apart from the engines and from AI Mode, with the sample size, on your own DataForSEO credit. | Partly"When your domain is cited as a source in an AI Overview, Position Tracking records this as a #1 ranking" — folded into rankings rather than reported apart; the AI toolkit's Organic Rankings says "whether or not your domain is cited in those AI Overviews". | Yes"AI Mode draws from a different source pool than AI Overviews - and Peec AI tracks your brand across both, separately." AI Overviews is a Starter model; since Jul 6, 2026 it also records "not-triggered AI Overviews so you can measure trigger rate". |
| Shows which AI crawlers fetched your pages | YesOur WordPress plugin on every plan, or your Cloudflare zone from Growth: which bots fetched which of the pages we published, how often and when last, with "nothing yet" against the pages nothing has come for. | PartlyA separate Log File Analyzer: "Upload or connect your server logs, and filter for user-agents like GPTBot, ChatGPT-User, OAI-SearchBot, and ClaudeBot." Not listed in the AI Visibility Base plan on the pages we read; the AI toolkit's own crawler check reads robots.txt. | Yes"Crawl Insights reveals AI bot activity directly from your server logs", down to "The specific user agent (e.g., GPTBot, ClaudeBot, PerplexityBot)", from CloudFront, Google Cloud CDN, Cloudflare, Vercel, WordPress, Akamai, a webhook or a log upload; Starter includes "4M bot visits". |
| Announces published pages to IndexNow | YesEach site has its own IndexNow key — made for it, or the one your SEO plugin already serves — and once the site serves it, the pages we place there are announced to Bing and the indexes that read IndexNow. | Not statedNot stated on the pages we read (Oct 10, 2026): the AI Visibility feature, pricing and help pages. Semrush's blog recommends IndexNow through Bing Webmaster Tools — advice, not a feature. | Not statedNot stated on the pages we read (Oct 10, 2026): peec.ai, its pricing, changelog, use cases and docs. |