TimeSaverBot – Multilingual AI Chatbot for WooCommerce & Live Chat vs VigIA – AI Visibility, Analytics & Control

Someone lands on your site at 11pm with a question. Nobody is online. They buy from whoever did answer. TimeSaverBot is an AI chatbot for WordPress and WooCommerce. It learns your existing pages and your product catalog, answers visitor questions in 46 languages, recommends products from your own stock, and collects contact details when nobody on your team is online. Built for WooCommerce stores, clinics and salons that take bookings, agencies, and any site that sells a service and answers the same questions all day. Setup is a wizard: pick your pages, pick a ready-made bot, done. No code, no theme edits, no separate sign-up — you are live in about five minutes. 30-day free trial. No credit card. Answers only from your own content — your pages, your FAQ, your products. Not from the open internet. No OpenAI API key — nothing to register, no token bills, no keys to paste into WordPress Deep WooCommerce integration — price, stock, variations, weight, dimensions, photos 46 languages, detected automatically — your content stays in one language Five ready-made bots — sales, support, bookings, e-commerce, or your own instructions Captures leads 24/7 — your team picks up a conversation that is already half done The plugin connects your site to the TimeSaverBot platform. The setup wizard creates your account for you. The bot answers from your site, not from the internet An AI chatbot is only worth having if you can trust what it tells your customers. TimeSaverBot builds every answer from the pages you chose, the FAQ you wrote and the products in your catalog. When it doesn’t have the answer, it says so and offers to take the visitor’s details instead of inventing something. Prices, stock, model numbers, SKUs and brand names come straight from WooCommerce, so they are right at the moment the customer asks. And there is no OpenAI account to open and no separate usage bill to watch — the platform handles the AI side. The bot knows your WooCommerce catalog The plugin reads your products through WooCommerce’s own API, so the bot answers like a salesperson standing in your stockroom: Price and sale price. “How much is it?” — “$24.90, on sale right now, normally $29.” Stock, down to the last unit — including the one that sold a minute ago to somebody else. Most integrations never notice that. Variations. “Do you have it in blue, size 42?” — “Blue 42 is in stock, $24.90. Red 42 is sold out.” Weight and package dimensions. “Will it fit a parcel locker?” — “2.4 kg, and the box is 30 × 20 × 15 cm.” Photo, brand, category, SKU and rating — the bot sends a real product card with a button through to the product page, and finds things the way customers ask: by brand, by product code, by category. Sold-out products too — “It’s out right now, leave your details” beats silence. It narrows down, as well: “something under $30”, “only what’s in stock”, “cheapest first”. Create, edit or delete a product and the bot knows moments later — no overnight update, nothing to re-import by hand. Import your whole catalog or a single category with its subcategories. WooCommerce is optional. Without it, everything else works exactly the same. 46 languages, and the bot picks the right one itself Most chat plugins offer a handful of languages and ask you to choose one. TimeSaverBot works out the language from the visitor’s first message and answers in it. A Polish visitor gets Polish. A Brazilian gets Portuguese. Nobody picks a setting. Your content stays in one language — yours. The bot understands what a question means, not just the words it is written in, so the answer is built from the page you already wrote and comes back in the visitor’s language. No translation plugin, no duplicate pages, no 46 versions of your FAQ Exact details still match exactly — model numbers, SKUs, brand names Right-to-left done properly — for Arabic, Persian, Hebrew and Urdu the whole chat window mirrors, not just the text The chat window’s own buttons and labels ship in 82 languages and regional variants, and the plugin’s admin screens in 75 From Arabic and Chinese to Polish, Portuguese and Thai — see the full list in the FAQ. Pick a bot and it works out of the box 📈 General Sales — services, B2B, landing pages. Answers, then guides toward an inquiry. 🎧 General Support — sites with documentation or a knowledge base. 📅 Service Order — clinics, salons, repair shops. Collects name, phone, service, preferred time. 🛒 E-commerce — advises from your catalog, compares products, answers on price, stock, delivery and payment. 🤖 Prompt Bot — for anything the four above don’t cover. You write the instructions: a bot that only screens candidates for your job openings, or one that answers strictly from your legal FAQ and refers everything else to a partner. Live in about five minutes Activate the plugin — the wizard starts on its own. Pick the pages the bot learns from. Your WooCommerce catalog imports at the same time. Choose one of the five bots above, or write your own instructions. Set your widget colors and text, with live preview. Done — the widget is already on your site. Every step after picking your pages can be skipped. The bot always knows the current state of your site Edit a page and the bot picks the edit up. Publish one and it is included. Delete it and it drops out — the bot never answers from a page that no longer exists. Pages, posts and your custom sections like Services or Projects Re-scan the whole site or a single page whenever you want Write FAQ answers by hand, or import them from CSV or JSON Everything syncs in the background and never holds up your editor A widget that fits your site Appears on every page automatically — no shortcode, no theme file to edit Your colors, button text and chat title, previewed live in the wizard Works on phones, tablets and desktops — on a small screen the chat opens out to fill it Runs in its own window inside your page, so your theme can’t break it and it can’t break your theme Conversations turn into customers Chatting is not the point. Getting the business is. TimeSaverBot asks the qualifying questions you would otherwise type out yourself, works out what the visitor actually wants, and takes their contact details before they click away. If nobody is online, you still get the lead — with the whole conversation attached. When your team is around, the same widget is your live chat: switch on Live operators and the bot hands the conversation over to a human instead of taking a contact. Everything from your WordPress admin One click, no second login — Chat, Leads and Knowledge Base open straight from the WordPress menu Your numbers in wp-admin — conversations, leads and conversion rate for the last 30 days, plus how much of your monthly dialog allowance is left All settings in WordPress — the bot’s instructions, its tone, when it hands over to your team, and how the widget looks Safe by default Your WordPress password is never sent anywhere Every connection is signed, and opening Chat or Leads uses a one-time key that expires after 60 seconds Your installation is tied to your domain — nobody can point it elsewhere Reinstalling puts everything back — your connection survives a delete by default, or one checkbox under TimeSaverBot → Help makes deletion clear it from your site instead Worth knowing before you install TimeSaverBot is a hosted service. The plugin is the WordPress side of it; the AI itself runs on the TimeSaverBot platform. Single-site WordPress only — multisite is not supported yet. Pricing 30 days free, no credit card required. After the trial the plugin needs a paid TimeSaverBot plan to keep answering. The entry plan is $26/month and includes 100 AI conversations; beyond that, conversations are $0.09 each. Larger plans bring the per-conversation price down. Your WordPress dashboard shows the month’s limit and what is left of it, so nothing runs up quietly. Every plan includes all 46 languages, even the cheapest one — you never pay extra for them. See current plans. Try it on your own site Install the plugin and activate it. The wizard opens by itself, learns the pages you pick, and puts the widget live. In about five minutes you can open your own site and ask your bot a question — in any of the 46 languages — and see what your visitors will get tonight. Third-Party Service Disclosure This plugin relies on the TimeSaverBot SaaS platform hosted at app.timesaverbot.com. The following external connections are made: Provisioning API (POST /Provision/WordPressInstall) — Called once during the setup wizard to create your workspace. Sends: site URL, installation ID, WordPress version, plugin version, admin email. Dashboard Summary API (GET /Provision/WordPressDashboardSummary) — Called when loading the Dashboard page. Returns aggregated usage metrics. Operation Token API (POST /Auth/CreateOperationToken) — Called when you navigate to Chat, Leads, or Knowledge Base. Issues a short-lived authentication token. Iframe embeds — Bot Settings and Widget Settings pages load the TimeSaverBot configuration UI inside an iframe from app.timesaverbot.com. Silent login redirects — Chat, Leads, and Knowledge Base menu items redirect to app.timesaverbot.com with automatic authentication. Chat widget script (embed.js) — Loaded on every frontend page after wizard completion. The script is served from widget.timesaverbot.com and renders the chat widget inside an iframe. It sends your tenant ID and channel ID as data attributes. All server-to-server API calls are signed with HMAC-SHA256 using a per-installation secret. No data is sent to any other third-party service. TimeSaverBot Terms of Service TimeSaverBot Privacy Policy Privacy TimeSaverBot connects to the TimeSaverBot SaaS platform at app.timesaverbot.com. This section documents all data transmitted. Data sent during provisioning (one-time, on wizard completion) Normalized site hostname (e.g. example.com) Installation UUID (locally generated, not tied to any personal data) Raw site URL, WordPress version, plugin version (diagnostic metadata) Admin email address (used to create a technical user for your workspace) Data sent during normal operation Dashboard: HMAC-signed GET request with installation ID header. Returns aggregate metrics only. Navigation (Chat/Leads/Knowledge Base): HMAC-signed POST request with installation ID and requested scope. Returns a one-time authentication token. Settings (Bot/Widget): After initial authentication, the iframe communicates directly between the browser and TimeSaverBot. The WordPress plugin does not relay this traffic. Data stored locally Installation ID, HMAC secret, tenant ID, connector channel ID, process ID, wizard state. All stored in the wp_options table under the tsvbot_wp_settings key. Data stored remotely Chatbot configuration, conversations, leads, and usage metrics are stored on the TimeSaverBot platform. See the TimeSaverBot Privacy Policy for retention and deletion policies. No additional third parties This plugin does not transmit data to any service other than app.timesaverbot.com.

VigIA (Spanish for “lookout” or “watchman”, incorporating “IA” – Spanish for “AI”) is a complete AI visibility toolkit for WordPress. Monitor 60+ AI crawlers, control access to your content, and optimize how AI systems discover and understand your site. What does VigIA do? Scores your AI visibility with a 100-point analyzer covering 20 checks across 5 categories Tracks AI crawlers visiting your site (GPTBot, ClaudeBot, PerplexityBot, and 60+ others) Provides detailed analytics with advanced filters, server-side pagination, and exportable reports with metadata banner Blocks unwanted crawlers via PHP (403 response) Manages robots.txt rules for AI crawlers with compliance monitoring Sends email alerts about crawler activity (daily, weekly, or monthly) Generates llms.txt files to help AI systems understand your site Serves markdown endpoints for posts, pages, taxonomy archives (categories, tags, WooCommerce product categories, custom taxonomies) and WooCommerce products with schema-like data Generates JSON-LD structured data with Site Identity and AI Discovery signals Exposes abilities for AI agents and automation tools (WordPress 6.9+) Key Features AI Visibility Analyzer * 100-point scoring system with letter grades (A+ to F) * 20 individual checks across 5 categories * Access & AI Discovery (37 pts): robots.txt, AI bot directives, Content Signals, llms.txt, sitemap, RSS feed * Structured Data & Semantic Context (25 pts): JSON-LD schemas, Open Graph, Twitter Cards, meta description, canonical URL * Content Structure & Readability (20 pts): heading hierarchy, semantic HTML5, image alt text, content/HTML ratio * AI Interaction & Distribution (8 pts): markdown delivery, AI share buttons * Access Performance (10 pts): TTFB measurement * Smart recommendations with direct links to VigIA features and plugin suggestions * Analyze any page on your site with URL autocomplete selector * Results cached for 24 hours with manual re-analyze option Analytics Dashboard * Total visits, unique crawlers, and pages crawled statistics * Timeline chart with daily breakdown * Category distribution (AI Training, AI Search, AI Assistant, Data Scraper) * Top crawlers and most crawled pages tables with paginated navigation * Share Buttons & AI-powered Summaries integration: see share button clicks per page * Recent activity log with content type and HTTP status columns (color coded by status family) * Advanced filters: multi-select crawler picker, content type, HTTP status code, and configurable date range * Server-side pagination with four-button pager (first, previous, next, last) — operates over the full database, not just the latest 500 rows * Period comparison functionality * CSV export with a metadata banner (site name, site URL, export type, date range, export timestamp, applied filters) * “Export filtered CSV” button that downloads exactly what the active filters return, with vigia-filtered-YYYY-MM-DD.csv filename * Content type detection distinguishes Home, Post, Page, Product, custom CPTs, Category archive, Tag archive, Date/Author archive, Feed, Sitemap, REST API, File, Admin / login attempts (/wp-admin, /wp-login.php), WordPress system (admin-ajax, xmlrpc, wp-cron, wp-comments-post), 404 Not found, and Other Crawler Blocking * Block crawlers via PHP with 403 Forbidden response * Quick block dropdown in analytics dashboard * Manage blocks from Extras page * Works on any server (Apache, Nginx, LiteSpeed, etc.) Robots.txt Management * Add Disallow rules for AI crawlers * Visual preview of your robots.txt * Compliance monitoring: see which crawlers ignore your rules * One-click blocking for non-compliant crawlers * Works with both physical and virtual robots.txt Email Alerts * Daily, weekly, or monthly reports * Three detail levels: Minimal, Normal, Complete * Non-compliant crawler warnings * Activity comparison with previous period Markdown for Agents * Serve posts, pages and any public post type as optimized markdown for AI agents * Serve taxonomy archive pages (categories, tags, WooCommerce product categories, custom taxonomies) as markdown — disabled by default, opt in per taxonomy * Dedicated .md URL endpoints (e.g., /your-post.md, /category/news.md, /product-category/electronics.md) * Accept: text/markdown content negotiation on posts and taxonomy archive pages * Discoverability via Link HTTP headers and HTML tags * YAML frontmatter for posts: title, date, modified, author, image, categories, tags, post type, lang * YAML frontmatter for taxonomy terms: title, description, url, type, taxonomy, parent, count, image (term meta), lang * WooCommerce product frontmatter adds schema-like fields: sku, product_type, price, regular_price, sale_price, currency, availability, stock_quantity, rating, rating_count, review_count * Taxonomy term body includes the term description (rendered through the_content), the list of direct child terms in hierarchical taxonomies, and an excerpt of the latest posts/products assigned to the term * Product listings inside product_cat archives include an inline summary with formatted price, “was X” on sale items, star rating and out-of-stock flag * Respects blocking rules (blocked crawlers get 403) and LLMs.txt exclusion filters * Per-term noindex detection from Yoast SEO, Rank Math, All in One SEO and SEOPress * Analytics integration: tracks markdown requests per crawler * X-Markdown-Tokens response header * Filters: vigia_markdown_post_eligible, vigia_markdown_term_eligible, vigia_markdown_term_posts_limit * Follows the Cloudflare Markdown for Agents standard LLMs.txt Generator * Select content by post type with one click * Filter by taxonomies (categories, tags, custom) * Manual include/exclude with AJAX search * Exclude by URL patterns (wildcards supported) * SEO plugin integration (auto-exclude noindex content) * Auto-regeneration (daily, weekly, monthly) * Robots.txt integration (add llms.txt and llms-full.txt references) * Generate llms.txt and llms-full.txt files * Full content or excerpt mode * Compatible with Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, and Native SEO NoIndexer JSON-LD Structured Data * Generate WebSite and Organization/Person schema for site identity * AI Discovery: ReadAction pointers to llms.txt, llms-full.txt, and Markdown for Agents endpoints * Social profiles and sameAs links for brand identity across the web * SearchAction for Google sitelinks search box * Media library integration for logo selection * SEO plugin conflict detection (Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework) * Choose output page (front page or any published page) * Live JSON-LD preview with real-time updates * Smart integration with LLMs.txt and Markdown for Agents features Supported AI Crawlers VigIA monitors 60+ AI crawlers including: OpenAI: GPTBot, OAI-SearchBot, OAI-AdsBot, ChatGPT-User Anthropic: ClaudeBot, Claude-SearchBot, Claude-User, Claude-Code Google: Google-Extended, GoogleOther, Gemini-Deep-Research, Google-NotebookLM Perplexity: PerplexityBot, Perplexity-User Meta: Meta-ExternalAgent, FacebookBot, Meta-WebIndexer Amazon: Amazonbot, Amzn-SearchBot, bedrockbot Mistral: MistralAI-User, MistralAI-Index Microsoft: BingBot ByteDance: Bytespider Apple: Applebot-Extended And many more… Privacy Focused VigIA stores visitor data locally in your WordPress database. No data is sent to external servers. Abilities API VigIA is one of the first WordPress plugins to implement the Abilities API introduced in WordPress 6.9. This API allows AI agents, automation tools, and external systems to discover and interact with VigIA’s functionality in a standardized, secure way. What are Abilities? Abilities are self-contained units of functionality that VigIA exposes through WordPress’s central registry. Each ability has defined inputs, outputs, and permissions, making it easy for automation tools to understand and use them. Available Abilities VigIA registers the following abilities: Analytics vigia/get-crawler-stats – Get statistics about AI crawler visits (total visits, unique crawlers, pages crawled) vigia/get-top-crawlers – Get a ranked list of most active AI crawlers vigia/get-top-pages – Get the most crawled pages on your site Blocking vigia/get-blocked-items – List all blocked crawlers and IP addresses vigia/block-crawler – Block a crawler by User-Agent pattern vigia/unblock-crawler – Remove an existing block Robots.txt vigia/get-robots-rules – Get current AI crawler rules in robots.txt vigia/add-robots-disallow – Add a Disallow directive for a crawler vigia/remove-robots-rule – Remove a robots.txt rule Use Cases Automated monitoring: AI agents can query crawler statistics and alert you to anomalies Reactive blocking: Automation tools can block crawlers that repeatedly ignore robots.txt External dashboards: Aggregate data from multiple WordPress sites with VigIA installed WP-CLI integration: Future command-line access through the Abilities API n8n / Make workflows: Build custom automation flows using VigIA’s abilities Requirements The Abilities API ships with WordPress 6.9 and later. On older WordPress versions, VigIA works normally but abilities and MCP are not available. MCP Server (Model Context Protocol) VigIA exposes its 9 abilities as native MCP tools to any MCP-compatible client (Claude Code, Cursor, Claude Desktop, Codex CLI, Antigravity, Continue, Cline, Zed and similar) using the official WordPress MCP Adapter. The adapter ships bundled with the plugin, so the MCP endpoint is active right after installation — no Composer step or terminal access required. Requirements WordPress 6.9 or later (provides the Abilities API) Quick connect (recommended) Open VigIA > Extras > MCP and click “Generate password and connection commands”. The plugin creates a dedicated Application Password named VigIA MCP and renders ready-to-paste commands for Claude Code, Cursor, Claude Desktop and a generic block (URL + Authorization header) for any other MCP client. The plain password is shown only once. If you lose it, revoke the entry from the same panel and generate a new one. Endpoint https://your-site.example/wp-json/vigia/v1/mcp The endpoint uses HTTP Basic auth with the WordPress Application Password. The user must have the manage_options capability. Connecting Claude Code Quick Connect builds the full command for you. The shape is: claude mcp add --transport http vigia https://your-site.example/wp-json/vigia/v1/mcp --header "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD" Claude Code merges the new entry into its config file automatically — no risk of breaking other servers. Connecting Cursor Save the JSON block from Quick Connect as ~/.cursor/mcp.json. You can also reach this file from inside Cursor at Settings → Cursor Settings → MCP. If the file already exists with other content, see the FAQ. Claude Desktop and other clients Claude Desktop does not speak HTTP MCP, so it needs a small bridge and a config file of its own. Any other client (Codex CLI, Continue, Cline, Antigravity, Zed, or your own) takes the two raw values Quick Connect exposes: the server URL and the Authorization header. Both cases are covered in the FAQ, together with how to merge VigIA into a config file that already exists without losing what is in it. Read-only mode If you only want your AI to consult VigIA (not change anything), enable “Read-only mode” in the MCP tab. While on, write actions (block, unblock, robots changes) return a permission denied error. Read actions (statistics, top crawlers, blocked items, robots rules) keep working. The toggle stores a vigia_mcp_read_only option that hooks into the vigia_can_write_via_abilities filter. Developers can still force read-only from a mu-plugin: add_filter( 'vigia_can_write_via_abilities', '__return_false' ); The mu-plugin filter at the default priority takes precedence over the toggle. Who can reach the endpoint The endpoint requires the capability to manage options, the same one every tool behind it already asked for. The vigia_mcp_transport_capability filter can lower that bar; each tool keeps its own permission check. After connecting Restart your MCP client after adding the server so it picks up the new tools. Then try a few prompts to confirm everything is wired up: “Show me VigIA crawler stats for the last 7 days.” “List the top 5 most crawled pages on this site.” “Add a robots.txt Disallow rule for TestBot and then list the current AI crawler rules.” The third example exercises a read + write + read round-trip, which is the most complete sanity check. Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.