ParseLess vs TimeSaverBot – Multilingual AI Chatbot for WooCommerce & Live Chat

ParseLess serves your WordPress content as clean Markdown to AI crawlers (via User-Agent detection) and on manual ?format=md requests. Same URL, same content, none of the theme chrome, navigation, widgets, or page-builder scaffolding that AI bots and CLI tools don’t need. It also exposes /llms.txt for the emerging AI-indexing standard, so models know where to find your content. Who is this for? 1. Developers using Claude Code, Cursor, Aider, or any CLI that feeds your own site content into an LLM. If you’ve ever piped a blog post into Claude or ChatGPT for analysis, rewriting, or summarization, you’ve watched it burn through tokens parsing nav menus, footer markup, and CSS classes that have nothing to do with your content. A typical WordPress page measured live: ~19,800 tokens of HTML for ~975 tokens of actual content — a 20x reduction just by stripping the theme. Heavy page-builder sites (Elementor, Divi) routinely hit 100x or more. That’s the difference between fitting a handful of pages in a context window and fitting dozens. Just append ?format=md to any post URL and pipe it straight into your tool of choice: curl https://yoursite.com/my-post/?format=md | claude "summarize this" 2. Site owners getting “high resource usage” warnings from their host because AI bots are hammering the site. GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and a dozen others crawl WordPress sites constantly. Each request renders your full theme, runs widget queries, loads page-builder assets, and ships hundreds of KB of HTML per page — most of which the bot discards before extracting the actual text. ParseLess intercepts these crawls and serves a tiny Markdown payload instead. You keep the AEO/SEO benefit of being indexed by AI search, without paying the server cost of rendering your full theme for every bot hit. Typical impact on AI bot traffic (measured on real WordPress pages): 95%+ less bandwidth per crawled page (typically 15–30x smaller; e.g. a 79 KB page → 4 KB. Heavy page-builder sites see 100x+) ~60–80% fewer database queries per request ~60% lower peak PHP memory per request ~50–80% faster Time To First Byte (measured 54% on a content-heavy page, 67% on a short one) On a site with 500 posts crawled monthly by major AI bots, that’s roughly gigabytes → tens of megabytes of monthly bandwidth and a fraction of the cumulative PHP execution time Numbers vary by theme and content. Heavier setups (Elementor, Divi, Avada) see the biggest savings; lightweight themes see less dramatic but still meaningful gains. The conversion is cached as a transient, so repeated bot hits cost almost nothing. How it works AI crawlers are detected by User-Agent and served Markdown automatically — no configuration required. Humans, search engines, and unknown bots receive your normal HTML output. ParseLess never affects what real visitors see. The ?format=md query parameter works on any post URL for manual preview or CLI piping. /llms.txt is published at your site root with a list of available content for AI indexers. Conversion happens once per post and is cached. Subsequent requests serve a single transient read. Features Automatic Markdown for known AI bots (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, CCBot, Google-Extended, Applebot-Extended, Bytespider, Meta-ExternalAgent, cohere-ai, and more) Manual preview and CLI access via ?format=md on any post URL /llms.txt endpoint for AI-indexing standards Respects noindex flags from Yoast SEO, Rank Math, and Genesis Skips private, draft, password-protected, and trashed posts Works with all public post types (configurable) Optional YAML frontmatter (title, URL, author, date, categories, tags, excerpt) Transient-based caching with configurable TTL Settings page at Tools → ParseLess for detection mode, bot list, cache TTL, post types, and llms.txt control Per-post meta box with Markdown preview and copy-to-clipboard Extensible via filters: md4ai_bot_list, md4ai_supported_post_types, md4ai_markdown_output, md4ai_cache_ttl, md4ai_should_serve_markdown Privacy and data collection When logging is enabled (off by default), ParseLess records the following for each Markdown request: Post ID, URL, and request timestamp The full User-Agent header A salted SHA-256 hash of the requester’s IP address (the raw IP is never stored) Matched bot identifier, bytes served, and whether the response came from cache IP hashes cannot be reversed from an email address, so the WordPress privacy exporter/eraser tools will report no personal data on demand. Logs are pruned daily according to the configured retention window (7/30/90/365 days, default 30). Site owners can disable logging or click “Delete all logged requests” at any time from Tools → ParseLess.

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.