NP Feed Doctor
Find the product-data gaps blocking clean WooCommerce feeds before they reach a connector: identifiers, content, images, price and stock, taxonomy, schema, channel requirements, and AI-readiness signals — with evidence, bounded previews, and review-before-write safe fixes.
→ A self-hosted catalog diagnostic that works before or beside your feed connector; beta access is operator-confirmed while the release remains controlled.
Inspect the exact catalog diagnostic before inviting it into a real store.
Match the protected beta ZIP, inspect six real WooCommerce workspaces on desktop and mobile, then check whether its local diagnostic boundary fits your operating model.
One public beta identity, one protected fulfilment artifact.
The product page, private current-version pointer and installed runtime all resolve to the same deterministic 0.3.0-beta.1 ZIP.
7157e8adc89faf205fdc747225e4be10d9c0970415f188b01d22d4af29de459eThe release has a verified technical trail, but broader store, theme, connector and catalog combinations still need operator-led staging. Request access so the exact fit can be reviewed before delivery.
Scan the catalog, open the evidence and test a safe repair.
Choose the channels that matter, run the deterministic fixture and work from the highest-risk product to the exact field. Only verified metadata repairs offer a preview and rollback.
A five-product fixture is ready
The scan applies the published 0.3.0-beta.1 weights and severity penalties. It never contacts a store or channel.
A five-product fixture is ready
The scan applies the published 0.3.0-beta.1 weights and severity penalties. It never contacts a store or channel.
What this proves
You can inspect the real scoring shape, evidence granularity and safe-fix boundary before installing. It does not prove channel approval, ranking or revenue.
Verified 0.3.0-beta.1 boundary: local catalog reads; no customers, orders, carts, payments, sessions, external OAuth, telemetry, AI calls or channel approval claim.
Experience NP Feed Doctor
Follow real shopper and merchant paths, inspect the interface at full size, then open the live demo when one is available.
See what is wrong before opening another feed dashboard
The demo catalog is scored across eight categories. The action center converts the score into exact queues instead of leaving you with a single red number.
- Exact severity counts and category scores
- Channel goals stay visible in context
- Each action names its bounded destination
This tour uses real product captures and documented behavior. It is not a performance benchmark or a promise of storewide uplift.
NP Feed Doctor is a local-first WooCommerce catalog diagnostic. It scans product and variation records inside WordPress, calculates a Catalog Health Score, and turns abstract “feed problems” into a product-level queue with issue code, severity, evidence, and a bounded next action.
The 0.3.0-beta.1 workspace is organized around six jobs: Overview, Issues, Safe fixes, Feed lab, Scans, and Settings. Use it before or alongside your existing feed exporter or channel connector. Preview profile-shaped XML or CSV rows, inspect the remaining populated fields on demand, export scan evidence, and schedule conservative background scans with retention controls.
Safe fixes are deliberately narrow. The plugin first builds a dry-run queue; an authorized WooCommerce manager selects the rows to apply. It can normalize or backfill supported metadata and record attribute-completeness follow-up, but it does not invent missing commercial facts. Product-data edits require review, and rollback notes stay attached to the queue.
The plugin reads catalog data only. It does not read customers, orders, carts, payments, sessions, checkout submissions, or ad audiences. It makes no automatic channel, analytics, telemetry, AI, or license API calls in this beta. Optional llms.txt and read-only agent-catalog signals are disabled until the merchant enables them, and no Google, Meta, TikTok, Bing, ChatGPT, Gemini, or other approval, inclusion, ranking, traffic, or revenue outcome is promised.
What it does
- One prioritized Catalog Health Score across identifiers, content, images, price and stock, taxonomy, schema, channel-feed readiness, and AI-readiness signals.
- Product-level evidence instead of a vague warning: issue code, severity, observed value, expected signal, and the affected channel goal.
- Review-before-write safe fixes: preview a bounded queue, select exact rows, apply supported metadata changes, and keep rollback notes. Missing commercial facts are not invented.
- Feed lab with profile-shaped XML and CSV previews, seven primary commerce fields first, expandable populated details, and capped downloads for inspection.
- Scheduled local scans, retained snapshots, JSON evidence export, channel-goal filters, and responsive task workspaces that remain usable at 390px.
- Catalog-only privacy boundary: no customer, order, cart, payment, session, checkout, or ad-audience reads; no automatic external calls in this beta.
- Optional llms.txt and read-only agent catalog are off by default, expose published product facts only when enabled, and never imply AI-shopping inclusion.
In the wild
Who this is for
Before connecting a catalog channel
Audit identifiers, descriptions, images, price, stock, taxonomy and schema before a feed exporter or connector turns product gaps into channel errors.
For agencies triaging a messy catalog
Use issue codes, evidence, filters and JSON snapshots to separate work the plugin can preview from commercial facts the merchant must supply.
For stores already using a feed plugin
Keep the existing connector as the submission owner. Use Feed Doctor as the local catalog preflight and evidence layer beside it.
vs feed exporter or channel connector
These tools own different jobs. NP Feed Doctor diagnoses and prepares catalog data locally; an exporter or connector maps and submits products to an external channel. Many stores need both, with one clear owner for each surface.
| Capability | NP Feed Doctor | feed exporter or channel connector |
|---|---|---|
| Primary job | Catalog diagnosis, evidence, and bounded remediation preview | Feed mapping, synchronization, or channel submission |
| Customer and order data | Not read; catalog-only scope | Depends on the connector and channel |
| External submission | No — diagnostics and local preview only | Often yes; verify the exact product |
| Approval guarantee | None | Channel decision; verify claims independently |
Why neuroplugin
- Evidence before automation
- Every queue starts with what was observed, why it matters, and what a bounded action would change. A score alone is not a workflow.
- Local-first by design
- Catalog scans, snapshots, schedules and fix queues stay in WordPress. Optional public signals remain disabled until the merchant chooses otherwise.
- Works beside the connector you already chose
- The plugin does not pretend to replace channel submission. It prepares and documents the catalog inputs that connectors depend on.
- A beta with an exact evidence trail
- The public version, release date, SHA-256, compatibility boundary, exact-ZIP runtime, desktop captures, and mobile captures all point to the same 0.3.0-beta.1 artifact.
By the numbers
Questions answered
- Does NP Feed Doctor submit products to Google, Meta, or another channel?
- No. It diagnoses catalog readiness and previews profile-shaped rows locally. Keep an official feed exporter or connector as the owner of external submission and validation.
- Does it guarantee Merchant Center approval or AI-shopping inclusion?
- No. Readiness scores are diagnostic signals. Approval, inclusion, policy compliance, ranking, traffic, and revenue remain decisions or outcomes outside the plugin.
- What store data does it read?
- Catalog data: products, variations, taxonomy, attributes, images, price, stock, and selected public or product metadata needed for diagnostics. It does not read customers, orders, carts, payments, sessions, checkout submissions, or ad audiences.
- Are safe fixes applied automatically?
- No. An authorized WooCommerce manager runs a dry preview, reviews before and after values, selects exact queue rows, and then applies supported changes. Missing brands, identifiers, or other commercial facts are not invented.
- Can I keep my current WooCommerce feed plugin?
- Yes. That is the intended boundary. Let the existing exporter or connector own mapping and submission; use NP Feed Doctor as the catalog preflight, evidence, and bounded remediation layer.
- Does the optional agent catalog expose private data?
- It is disabled by default. When a merchant enables it, the read-only endpoint and llms.txt signal use published product facts only. Review the output and caching path on staging before enabling any public endpoint.
- Why is access operator-confirmed during beta?
- The package is runtime-verified, but this is still a controlled beta. We confirm the exact WooCommerce, WordPress, PHP, theme, catalog size, feed stack, staging path, and support handoff before issuing the protected package.
Protect more of the revenue journey
Turn local PrestaShop SEO evidence into a prioritized, reviewable action queue—without ranking guarantees or obsolete indexing promises.
Self-hosted WooCommerce product search with three display modes, typo recovery, synonyms, facets and result add-to-cart. Core 1.3.1 is available only through a controlled pilot.
Free-shipping progress on product, mini-cart, cart and checkout, plus a configured weekday delivery window on product, cart and checkout.
Ready to add NP Feed Doctor?
Find the product-data gaps blocking clean WooCommerce feeds before they reach a connector: identifiers, content, images, price and stock, taxonomy, schema, channel requirements, and AI-readiness signals — with evidence, bounded previews, and review-before-write safe fixes.