Fix the product data before your feed connector exports the problem.
NP Feed Doctor is the local catalog preflight beside your WooCommerce feed plugin. Run the bounded demo, open the issue evidence, preview one safe fix, and decide whether the verified 0.3.0-beta.1 workflow fits your store. It diagnoses locally; it does not submit products or promise channel approval.
A connector can transport product data. It cannot make missing facts true.
Identifiers are absent or malformed
A connector can map an identifier field, but it cannot know the real brand or manufacture code when the catalog never stored it.
Product meaning is too thin
Short titles, empty descriptions, and incomplete attributes reduce the evidence available to feeds, schema, search, and shopping agents.
Commerce basics disagree
Missing primary images or inconsistent price and availability signals should be diagnosed at the product source before export.
Every surface tells a different story
Taxonomy, page facts, JSON-LD, and feed fields can drift. A useful audit shows the observed evidence path, not only a generic warning.
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 a fictional catalog, inspect evidence, and preview a safe fix.
Nothing is connected to a store or channel. The fixture stays in this browser and models the release scoring and review boundary.
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.
Keep diagnosis separate from submission.
NP Feed Doctor owns
- Scan product and variation evidence locally
- Score and prioritize product-level issues
- Preview bounded XML/CSV rows
- Build review-before-write safe-fix queues
Your feed connector owns
- Map fields to the external destination
- Authenticate with the channel
- Submit or synchronize products
- Return official channel validation results
From unknown catalog risk to reviewed next action.
- 01
Run a bounded scan
Start with a conservative product limit and explicit channel goals.
- 02
Open the evidence
Trace severity and issue code to the observed product value and expected signal.
- 03
Preview supported fixes
Generate a dry-run queue; review before/after and rollback notes without writing.
- 04
Verify the connector separately
Stage the exact feed mapping, submission, cache, and channel validation path.
The page demo and the packaged plugin tell the same story.
Know exactly what this diagnostic does not do.
- No customer, order, cart, payment, session, checkout, or ad-audience reads.
- No product submission, OAuth, channel API writeback, analytics, telemetry, or AI call in this beta.
- No approval, inclusion, policy, ranking, traffic, conversion, or revenue guarantee.
- Optional llms.txt and read-only agent catalog stay off until the merchant enables them.
Choose it for the catalog-preflight job, not for a promise it cannot make.
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.
Bring the exact store stack, not just a plugin wishlist.
Review the release page for the version, SHA-256, compatibility boundary, screenshots, install path, and controlled-beta terms. We confirm WordPress, WooCommerce, PHP, theme, catalog size, existing feed stack, staging, and support handoff before protected delivery.