Linux 软件免费装
Banner图

Seekmodo Search

开发者 numinix
更新时间 2026年9月23日 02:43
PHP版本: 8.0 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce search autocomplete typeahead ai-search

下载

0.11.60 0.11.59 0.11.62 0.11.61 0.11.63 0.11.64

详情介绍:

Seekmodo Search replaces the built-in WordPress site search (and the WooCommerce product search, when WooCommerce is active) with an AI-powered search experience served by the Seekmodo platform at mcp.seekmodo.com. One plugin, two activatable verticals: What you get: External service dependency. Seekmodo Search is the WordPress connector for the Seekmodo AI search platform. The platform is a hosted service operated by Numinix Technology Inc. at https://mcp.seekmodo.com and https://admin.seekmodo.com. The plugin connects your site to a Seekmodo tenant via an HMAC-signed pairing flow; once paired, the plugin sends indexable post / product data to mcp.seekmodo.com and queries it for search results, typeahead suggestions, and click telemetry. Free trial. Every Seekmodo plan ships with a 14-day free trial at $0 — full features, unlimited searches, no card required upfront. Cancel before day 14 and you pay nothing. After the trial, plans start at $29/month. Pricing details, including how the plan auto-sizes to your real traffic during the trial: https://seekmodo.com/pricing. What happens if you stop paying. The plugin does not break your site. If the gateway is unreachable, your subscription lapses, or you simply uninstall the plugin, every search entry point falls back to native WordPress / WooCommerce search inside the same request. No white screens, no fatal errors, no broken search box. Privacy + data handling. https://seekmodo.com/legal/privacy lays out the full picture, but in short: searchable post / product content you choose to index is sent to mcp.seekmodo.com; visitor search queries and clicks are sent to mcp.seekmodo.com as telemetry; no personal data about your visitors leaves your site unless you opt in to additional analytics integrations from the Seekmodo admin. The plugin self-checks for stale indexes, configuration drift, and update availability — all such phone-home requests are vanilla HTTPS GETs that carry no tenant ID and no site-identifying data; they're static-cacheable from our perspective.

安装:

Either:
  1. In WordPress admin, go to Plugins → Add New and search for "Seekmodo".
  2. Click Install Now on "Seekmodo Search", then Activate.
Or upload manually:
  1. Download the latest zip from https://seekmodo.com/plugins/wordpress.
  2. Upload via Plugins → Add New → Upload Plugin → choose the zip → Install Now → Activate.
Then in either case:
  1. Go to Settings → Seekmodo Search → Connect to Seekmodo.
  2. Click Start free trial / sign in and approve the pairing on seekmodo.com.
  3. (Optional) Run wp seekmodo index --full to seed your tenant immediately. (The plugin will otherwise reindex incrementally on its own.)
  4. Flip search mode from shadow to active in the connector settings once you've spot-checked a few searches.
Headless / CI install: wp plugin install seekmodo --activate wp seekmodo connect --tenant=<tenant_id> --secret=<shared_secret> wp seekmodo index --full wp option update seekmodo_wp_mode shadow

屏幕截图:

  • **Settings → Health + indexable types.** Mode / breaker readouts,
  • **Storefront suggest widget.** Gateway-ranked products, categories,

升级注意事项:

0.11.60
  • New: search-suggestions dropdown is enabled by default (opt out in Settings or via filters).
  • Fix: bulk index pushes no longer abort at the 2s search timeout — full reindexes report real counts.
0.11.59
  • Security: All $_SERVER inputs are properly sanitized through ServerInput helper class per WordPress.org Plugin Review requirements.
  • wordpress.org: GET /images is read-only (no public mark_dirty post meta writes).
0.11.58
  • wordpress.org: GET /images is read-only (no public mark_dirty post meta writes).
0.11.57
  • Commerce typeahead: when cloud/Enhanced Native returns no rows, fall back to WooCommerce products (not blog posts).
0.11.56
  • wordpress.org: uninstall.php no longer reads DOCUMENT_ROOT; runtime $_SERVER already via ServerInput since 0.11.52.
0.11.54
  • Heal broken suggest thumbs: durable ProductImage URLs, /images hydrate, commerce index cron.
0.11.53
  • Recommendations hover stacking: overflow-y visible + raised z-index so theme card hovers are not clipped.
0.11.52
  • wordpress.org review: sanitize/validate $_SERVER (and related) inputs early via ServerInput helper.
0.11.51
  • wordpress.org review: Tested up to in readme.txt only; ship Suggest/Ask TS source; remove static ABSPATH .well-known writes; clear stale over_quota sticky mid-trial.
0.11.50
  • wordpress.org review: drop source maps with CDN URLs from the package, JWKS via wp_remote_get only, nonce-gate cloud-suggest-denied, tighter inline-script / placeholder escaping.
0.11.49
  • Plugin Check i18n: literal __() strings in SuggestLabels (no variable text/domain).
0.11.48
  • Fix: WooCommerce add-to-cart telemetry caps — 15-minute product dedupe, 30 ATC/session/day, 120 ATC/IP/hour — stops scraper floods from inflating fleet-health funnels.
0.11.41
  • Fix: Suggest paints thumbnail_url for content posts; hides price_range on content vertical.
0.11.38
  • Fix: Multilingual Suggest dropdown no longer empties from mixed-locale /v1/suggest rows (serp filter_by lang + over-fetch + typeahead merge).
0.11.37
  • Fix: Polylang language-switch SERP no longer empties when gateway cache ignores lang (localize IDs + per-lang fetch buckets).
0.11.36 Suggest View all SERP links keep the active Polylang/WPML language path prefix. 0.11.35 Suggest chrome i18n: locale label packs + web-components 0.4.5 labels attribute support. 0.11.34 WordPress.org review follow-ups: enqueue inline assets, sanitize shopper inputs, uploads subdirectory for shadow logs, no default site-root writes. 0.11.22 Fixes Enhanced Native SERP order when themes force chronological sorting over relevance. 0.11.21 Stronger Enhanced Native title-phrase ranking so exact titles beat long body matches. 0.11.20 Improves Enhanced Native ranking: exact whole-word matches and adjacent title phrases outrank prefix/partial noise (Lead vs Leaders). 0.11.18 Fixes commerce-only storefronts: unscoped /?s= searches now claim the commerce swap so search_event_id is stamped for click tracking. 0.11.17 Fixes content SERP click tracking: search_event_id is stamped for /?s= searches so clicks count again (POCO Marine fleet health). 0.11.16 Fixes WooCommerce add-to-cart and purchase tracking: conversion hooks always register, flush with clicks instead of starving, and no longer drop decimal quantities. 0.11.10
  • Stamp search_event_id on add_to_cart / purchase for LTR last-touch linkage.
0.11.9
  • Shopper-context parity for typeahead + conversion events (session_id / ua / referer).
0.11.8 Documents HMAC auth_fail / signature_mismatch soft-degrade: Gateway\Client returns null so native WP/Woo search keeps serving during secret drift. 0.11.7 WordPress.org compliance: text domain seekmodo, no custom updater, branding off by default, privacy IP/UA disclosure. 0.11.6 WordPress.org submission readiness: vendored web-components bundle (no default CDN), complete uninstall cleanup, Tested up to 7.0, privacy-policy guide text, Health widget restricted to admins. 0.6.0 SM-606 Universal Suggest Widget. When the "Enable connector typeahead UI" master toggle is on, v0.6.0 swaps the legacy flat-row vanilla-JS dropdown for the new <seekmodo-suggest> web component, which renders the rich /v1/suggest envelope (recent + trending + keywords + products + categories + did-you-mean + "View all N results" CTA) and shares its UX with the BigCommerce / Zen Cart / AKS connectors. Existing sites can opt back into the legacy dropdown for one major- version cycle via Settings → Seekmodo → "Use legacy flat-row typeahead" or the new seekmodo_wp_suggest_legacy option. Bundle adds a single ~7 KB gzip JS asset under assets/suggest/. Adds a public POST /wp-json/seekmodo/v1/browser-token route so long-running tabs can refresh the gateway-direct token without a page reload. 0.5.3 Two follow-ups from PM-303. Operator UX: wp seekmodo index --full now covers BOTH verticals (content + commerce) by default and accepts a new --vertical=content|commerce|all flag. Pre-0.5.3 it only ran the content indexer, forcing commerce-only operators to drop into wp eval '\Numinix\SeekmodoWordPress\Commerce\Indexer::reindexFull();'. Safety: a stricter write-side host-lock gate (DomainLock::canIndex()) fails closed by default on non-prod hosts (dev.*, staging.*, stage.*, test.*, qa.*, preview.*, beta.*, preprod.*, sandbox.*) when the storefront-host lock is self-referential — the exact regression that put dev.pocomarine.com URLs into POCO's production Typesense index after the prod cutover. Read paths (typeahead, search swap) are unchanged. Operators with a legitimate non-prod indexing setup (e.g. paired to a separate *-dev tenant) opt back in via: add_filter('seekmodo_allow_nonprod_indexing', '__return_true'); in a mu-plugin. Mandatory upgrade for any tenant with a paired dev / staging WordPress install. 0.5.2 Hotfix for the gateway-direct typeahead introduced in v0.5.0. The storefront browser script was rendering an empty "No results" state on commerce-vertical sites because the canonical commerce row from /v1/typeahead (per CONNECTOR_TYPEAHEAD_SPEC.md) ships rows as name / url / image / in_stock, while the renderer only knew the legacy WP REST proxy shape (title / permalink / image_url / stock_status). The gateway-direct fast path therefore looked up r.title on every row, found undefined, and skipped them all — the user saw "No results" for every keystroke even though the wire returned 8 rows. Mandatory upgrade for any commerce-vertical install running v0.5.0 or v0.5.1. 0.5.1 Self-healing cache flushes. The connector now detects on-disk version bumps on the very first request after any deploy (rsync, wp-cli, or WordPress's native upgrader) and fans out cache invalidations to WP Rocket, LiteSpeed, W3 Total Cache, WP Super Cache, WP-Optimize, Hummingbird, Cache Enabler, Pantheon, Kinsta, Cloudflare WP, plus OPCache and the WordPress object cache. Fixes the "I deployed v0.5.0 but the site still loads v0.4.0" class of regression on hosts with WP Rocket page + minify caching configured for 1 year. Mandatory upgrade if you have any page-cache plugin installed. 0.5.0 Performance: typeahead now talks directly to the Seekmodo gateway from the storefront browser, skipping the WordPress REST hop. Drops the per-keystroke latency from ~2 seconds (WordPress full-stack boot on each request) to ~80–150 ms on heavy WooCommerce / Wordfence sites. Also adds a 32-entry client-side LRU cache so backspace + retype on a previously-fetched prefix renders instantly without a network round trip. Falls back to the WordPress REST endpoint automatically on any gateway-direct failure (token expiry, gateway 5xx, breaker open) — your search bar never breaks. 0.4.0 New feature: drop-in typeahead dropdown UI. The connector now ships a vanilla-JS search-suggestions box that auto-binds to your theme's <input type="search"> / <input name="s"> and renders gateway- powered results as you type, with vertical-aware row shapes (blog posts vs WooCommerce product cards). Default-OFF — flip it on from Settings → Seekmodo Search → Typeahead dropdown when you're ready, or leave it off if your theme already provides its own typeahead. Optional "Powered by Seekmodo" footer is opt-in (white-label by default). 0.3.4 New feature: editorial post-type ranking priority. Search results can now be bucket-sorted so that pages outrank blog posts (or any other order you specify) while textual relevance is preserved within each tier. No-op upgrade for sites that don't set the new option — gateway-relevance order keeps flowing through untouched. 0.3.3 Critical fix: the v0.3.2 pair-callback REST route was registered behind is_admin() so it never appeared on the server-to-server callback POST from seekmodo.com. Pairing was still impossible. v0.3.3 lifts the registration out of the admin-only block. Mandatory upgrade for anyone who hasn't paired yet. 0.3.2 Critical fix: the "Connect to Seekmodo" pairing flow has been rebuilt on the canonical install_token + signed-JWT protocol. v0.3.0 / v0.3.1 sent legacy nonce / return_to query params that seekmodo.com rejects with "This link is incomplete" — pairing through the browser was impossible. Superseded by v0.3.3 — install that one instead. 0.3.1 Bug fix: the "Connect to Seekmodo" button silently redirected to the WP admin homepage instead of seekmodo.com (wp_safe_redirect() rejecting the off-site host). Pairing was impossible without manual wp-cli fallback. Superseded by v0.3.2 — install that one instead. 0.3.0 Commerce vertical realigned to the gateway's Typesense schema — WooCommerce indexing now actually works (was 400'ing every upsert). Schema-version auto-promotes a one-time full reindex on the commerce side; content vertical is undisturbed. Ships the self-service "Promote dev to production" admin card so merchants can flip their canonical from a dev site to production without an operator round-trip. Worth picking up before standing up your WooCommerce dev site. 0.1.4 Adds WordPress.org Plugin Directory listing support: the Update URI header now routes update checks to seekmodo.com so we can ship hot-fixes faster than the w.org SVN sync cadence. No upgrade work required; just update. 0.1.3 Per-tenant "Powered by Seekmodo" branding toggle. Off by default; opt-in for partner sites. 0.1.0 Initial public release.

常见问题:

Do I need a Seekmodo account?

Yes. Seekmodo Search is the WordPress connector for the Seekmodo hosted AI search platform; the plugin itself is free and GPLv2, but it needs a paired Seekmodo tenant to do its job. Every plan ships with a 14-day free trial at $0 with full features and unlimited searches. After the trial, plans start at $29/month. Pricing details: https://seekmodo.com/pricing.

Do I need WooCommerce?

No. The content vertical works on any WordPress site (posts, pages, public custom post types). The commerce vertical activates automatically when WooCommerce is detected, and idles otherwise.

What happens if the gateway is down?

Every gateway-talking entry point falls through to native WP_Query (or WC_Query for products) inside the same request. Visitors never see an empty results page. A per-tenant circuit breaker prevents repeated timeouts from compounding, and Seekmodo health metrics auto-demote the connector back to native search if our gateway is unhealthy.

What happens if I stop paying / cancel my subscription?

Same as the previous answer. The plugin stays installed, the gateway-talking entry points start returning "no results" (since the tenant is gated), and every entry point falls back to native search in the same request. Your site keeps working; you just stop getting AI relevance. Re-pairing with a paid tenant restores full functionality.

Will this work on a staging clone?

Yes — Seekmodo locks each tenant to a canonical storefront host. Staging / dev hosts are auto-detected and return no-op from every gateway-talking entry point, so your production search index is never overwritten by a non-production deploy.

Where are my credentials stored?

In wp_options (seekmodo_wp_tenant_id, seekmodo_wp_shared_secret). wp seekmodo connect can be re-run any time to rotate the pair.

Where does the plugin send data?

Indexable post / product content goes to mcp.seekmodo.com (the gateway). Visitor search queries and clicks go to mcp.seekmodo.com as telemetry. The update check (12 h cadence) goes to seekmodo.com/api/plugins/seekmodo. Configuration pull (5 min cadence) goes to mcp.seekmodo.com/v1/tenant/snapshot. All gateway-bound requests carry an HMAC signature derived from the pairing secret. Full details in https://seekmodo.com/legal/privacy.

Does the plugin support translations?

The admin UI is localised via the seekmodo text domain and /languages/ directory. We ship English (en_US) as the source locale; contributions for other locales are welcome.

How do I get help?

Where is the human-readable source for the Suggest JavaScript?

The production Suggest bundle (assets/suggest/seekmodo-suggest.global.js) is a minified IIFE built from @seekmodo/web-components. Readable TypeScript for that bundle (and for the Ask IIFE / full web-components ESM) ships inside the plugin at assets/suggest/src/. See assets/suggest/SOURCE.md for the entry → file map, rebuild steps (npm install + npm run build in the web-components package), and notes on the inlined SDK copy under assets/suggest/src/vendor/seekmodo-sdk/. Ask and full ESM pointers: assets/ask/SOURCE.md, assets/web-components/README.md.

更新日志:

0.11.64 0.11.63 0.11.62 0.11.61 0.11.60 0.11.59 0.11.58 0.11.57 0.11.56 0.11.55 0.11.54 0.11.52 0.11.51 0.11.50 0.11.49 0.11.46 0.11.45 0.11.44 0.11.41 0.11.38 0.11.37 0.11.36 0.11.35 0.11.34 0.11.33 0.11.22 0.11.21 0.11.20 0.11.18 0.11.17 0.11.16 0.11.15 0.11.14 0.11.13 0.11.10 0.11.9 0.11.8 0.11.7 0.11.6 0.11.5 0.11.4 0.11.3 0.11.2 0.8.9 0.8.8 0.8.7 0.8.6 0.8.4 0.8.3 0.8.2 0.8.1 0.8.0 0.6.0 0.5.3 0.5.1 0.5.0 0.4.0 0.3.4 0.3.3 0.3.2 0.3.1 0.3.0 0.1.4 0.1.3 0.1.2 0.1.1 0.1.0