StoreSteadyStoreSteady
Summer 2026 / StoreSteady Research

32 of 40 crawled Kitchen/Coffee candidate stores exposed enough public PDP evidence for attribute-readiness evaluation.

StoreSteady measured a frozen Kitchen/Coffee crawl gate with deterministic public-evidence parsers. The report publishes the category-level evaluability rate and keeps one-layer product-family counts as raw diagnostics, not family-level rates.

For this report, StoreSteady evaluated a frozen corpus of 40 HTTP-only crawled Shopify storefronts selected from 53 valid Kitchen/Coffee candidates. Freeze: 2026-06-09. Evaluation window: 2026-06-09 HTTP-only crawl gate ending 2026-06-09T16:39:40.597Z.

Run a store-specific scan for public dimensions, capacity, compatibility, care, material, included components, safety/manual, and return-path evidence. The result is evidence for your store, not a projection from the benchmark.

Check your Kitchen/Coffee attribute readiness
Evidence funnel
Valid candidates
53
Frozen Kitchen/Coffee prospect pool after invalid URL and duplicate/same-operator exclusions.
Stores crawled
40
HTTP-only scanner-shaped crawl. No Firecrawl/provider-backed rendered fallback or production scanner writes.
Category-evaluable stores
32
80% of crawled stores; Wilson 95% CI 65.2% to 89.5%.
Excluded stores
8
5 empty or blocked; 3 completed with PDP N below 2.
Product-family cuts
raw counts only
No one-layer family cut cleared the N >= 30 floor for public segmented rates.

Published metric quality

MetricTierEvaluable NFinding NFlagged NNon-finding NRateWilson CIQualityCaveat
Category-evaluable public Kitchen/Coffee attribute evidence
kitchen_coffee_category_evaluable_public_attribute_evidence
Headline403232880%65.2% - 89.5%deterministicDeterministic public PDP evidence gate. Measures whether stores exposed enough public Kitchen/Coffee evidence to evaluate the rubric; it does not validate safety, compliance, ranking, checkout, or private feed state.
Empty or blocked crawl exclusions
kitchen_coffee_excluded_empty_or_blocked
Limitation40553512.5%5.46% - 26.1%deterministicAccess and empty-crawl states stay separate from category-evaluable stores and from missing PDP evidence.
Completed stores below the PDP evidence floor
kitchen_coffee_excluded_pdp_n_lt_2
Limitation4033377.5%2.58% - 19.9%deterministicCompleted stores with fewer than two PDPs are not blended into the category-evaluable denominator.
One-layer product-family counts
kitchen_coffee_one_layer_family_counts
Not rate-publishednot publishednot published--not publishednot publisheddeterministicRaw counts only: coffee_equipment: 20/20 evaluable; cookware_bakeware: 11/10 evaluable; kitchen_tools_cutlery: 2/2 evaluable; unclassified_kitchen_coffee: 7/0 evaluable.
Parser smoke rows classified
kitchen_coffee_parser_smoke_rows_classified
Not rate-published5454540not publishednot publisheddeterministicThe 3-store parser smoke proves rubric/parser shape only; the public headline denominator is the 40-store STO-503 crawl gate.
Kitchen/Coffee V1 rubric and parser validation smoke
Stores
3
Deterministic Kitchen/Coffee parser smoke.
PDPs
6
Eligible public PDPs.
Rows
54
Source-mapped attribute rows.
Parser
kitchen-coffee-public-evidence-parser.v1
Deterministic parser support.
StateRowsInterpretation
satisfied_visible_and_spec_shaped25State retained in the row artifact for recomputation.
satisfied_visible_text_only4Buyer-visible page text satisfied the rubric, without a spec-shaped field.
satisfied_policy_or_footer4A public policy or footer path satisfied the rubric.
missing_public_evidence21The parser found no public evidence for this attribute.
AttributeDefinitionExternal source fieldsSmoke states
product_type_use_casePublic PDP evidence identifies the kitchen or coffee product type and the intended buyer use case.Google: title, description, product_type, google_product_category
OpenAI/ACP: title, description, category, product_type
Shopify: product category, product type, category metafield entries
satisfied_visible_text_only: 4; missing_public_evidence: 2
dimensions_weight_fitPublic PDP evidence exposes dimensions, footprint, clearance, diameter, length, or weight for comparison and counter-fit questions.Google: product_length, product_width, product_height, product_weight
OpenAI/ACP: dimensions, weight, attributes
Shopify: measurements, product dimensions, variant metafield entries
satisfied_visible_and_spec_shaped: 3; missing_public_evidence: 3
capacity_servingPublic PDP evidence gives usable capacity in cups, quarts, liters, milliliters, ounces, servings, tank size, hopper size, or bowl size.Google: unit_pricing_measure, description, product_detail
OpenAI/ACP: attributes.capacity, description
Shopify: capacity, volume, category metafield entries
satisfied_visible_and_spec_shaped: 3; missing_public_evidence: 3
compatibility_fitPublic PDP evidence names compatible appliances, models, parts, pods, filters, heat sources, stovetops, or ovens.Google: product_detail, mpn, gtin, description
OpenAI/ACP: mpn, gtin, attributes.compatibility, description
Shopify: compatible products, model, category metafield entries
satisfied_visible_and_spec_shaped: 3; missing_public_evidence: 3
care_cleaning_partsPublic PDP evidence explains cleaning, seasoning, maintenance, dishwasher-safety, hand-wash status, removable parts, replacement parts, filters, gaskets, lids, or burrs.Google: product_detail, description
OpenAI/ACP: attributes.care, description
Shopify: care instructions, replacement parts, category metafield entries
satisfied_visible_and_spec_shaped: 6
material_food_contactPublic PDP evidence names material, coating, construction, or food-contact-relevant claims such as stainless steel, cast iron, ceramic, silicone, nonstick, BPA, PFAS, PTFE, lead, or cadmium.Google: material, product_detail, description
OpenAI/ACP: material, attributes.material, description
Shopify: material, coating, category metafield entries
satisfied_visible_and_spec_shaped: 3; missing_public_evidence: 3
included_components_setPublic PDP evidence states included pieces, lids, filters, accessories, components, set contents, or in-the-box details.Google: title, description, is_bundle, product_detail
OpenAI/ACP: attributes.included_components, description, group_id
Shopify: set contents, included accessories, category metafield entries
satisfied_visible_and_spec_shaped: 3; missing_public_evidence: 3
safety_certification_manualPublic PDP evidence shows safety warnings, certifications, manual links, use constraints, model details, energy labels, voltage, wattage, or recall-sensitive identifiers without classifying whether the product is safe or compliant.Google: certification, energy_efficiency_class, mpn, product_detail
OpenAI/ACP: certifications, mpn, attributes.safety, description
Shopify: certification, manual, safety attribute entries
satisfied_visible_and_spec_shaped: 4; missing_public_evidence: 2
return_shipping_pathPublic store evidence links to or states return, refund, exchange, shipping, delivery, damage, or heavy-item policy expectations before purchase.Google: shipping settings, return policy settings
OpenAI/ACP: shipping_policy, return_policy, accepts_returns, return_deadline_in_days
Shopify: store policy surface, return policy surface, shipping policy surface
satisfied_policy_or_footer: 4; missing_public_evidence: 2

Selection artifact: 3 store, 6 PDPs, selected by deterministic rules. Public artifacts expose aggregate counts, hashes, or surface pointers only, not merchant names, domains, raw URLs, raw titles, or page text.

Store Check

The useful next step is checking whether your own Kitchen/Coffee PDPs expose buyer-facing attribute evidence.

Run a store-specific scan for public dimensions, capacity, compatibility, care, material, included components, safety/manual, and return-path evidence. The result is evidence for your store, not a projection from the benchmark.

Check your Kitchen/Coffee attribute readiness

Detector primitives

kitchen_coffee_public_evidence_parser_v1

Kitchen/Coffee public evidence parser

54 parser-smoke rows classified before corpus expansion

Deterministic regex/state parser only. It measures public evidence presence and does not validate product quality, safety, compliance, ranking, or agent behavior.

sto_503_denominator_gate

STO-503 denominator gate

32 category-evaluable stores out of 40 crawled stores

HTTP-only crawl mode is conservative and may undercount stores needing rendered fallback. No provider-backed rerun was approved or used.

one_layer_product_family_counts

One-layer product-family counts

coffee_equipment: 20/20 evaluable; cookware_bakeware: 11/10 evaluable; kitchen_tools_cutlery: 2/2 evaluable; unclassified_kitchen_coffee: 7/0 evaluable

Family labels are diagnostics for corpus composition. They are not published as segmented rates because each family cut is below N >= 30.

Methodology summary

Selection rule: Start from 53 valid Kitchen/Coffee candidates, sort candidates by deterministic hash rank, crawl the first 40 with HTTP-only scanner-shaped collection, and count a store as category-evaluable only when at least two classified PDPs and two detector-hit PDPs anchor Kitchen/Coffee public evidence at one product-family layer.

What StoreSteady Measured

StoreSteady measured whether crawled Kitchen/Coffee candidate stores exposed enough public PDP evidence to evaluate a source-mapped Kitchen/Coffee attribute-readiness rubric.

The V1 rubric covers product type and use case, dimensions and fit, capacity, compatibility, care and parts, material and food-contact evidence, included components, safety or manual evidence, and return or shipping path evidence.

  • Store-level denominator: 40 HTTP-only crawled candidate stores.
  • Category-evaluable numerator: 32 stores with at least two classified PDPs and two detector-hit PDPs.
  • Product-family labels stop at one layer and are used only as raw diagnostic counts.

What StoreSteady Did Not Measure

The report does not validate product quality, product safety, food-contact truth, recall status, legal compliance, private Shopify setup, Google Merchant Center setup, OpenAI feed state, ACP compliance, checkout success, agent ranking, recommendations, conversion, or revenue.

Public absence is not treated as proof that a merchant lacks private attributes or connected feed data.

Corpus And Exclusions

The STO-503 crawl gate selected 45 candidates from 53 valid candidates and crawled 40 stores in the initial tranche.

32 stores were category-evaluable; 5 were empty or blocked; 3 completed but did not clear the PDP evidence floor.

Quality Gates

No LLM judgments were used for this report section; StoreSteady used deterministic parsers only.

The published headline uses the STO-503 store-level denominator and Wilson 95% confidence interval. The STO-467 3-store parser smoke is validation support, not the public headline denominator.

One-Layer Family Counts

Family labels are inferred from public PDP evidence at one product-family layer only. StoreSteady did not chase sub-subcategory validation such as individual coffee-machine part compatibility or battery-size-style attributes.

Diagnostic counts: coffee_equipment: 20/20 evaluable; cookware_bakeware: 11/10 evaluable; kitchen_tools_cutlery: 2/2 evaluable; unclassified_kitchen_coffee: 7/0 evaluable.

Limitations

  • HTTP-only crawling is conservative and may undercount stores that require rendered fallback.
  • The report measures public evidence presence and evaluability, not product quality, product safety, compliance truth, ranking, recommendation, checkout, conversion, or revenue impact.
  • Family-level cuts are below the N >= 30 public-rate floor and are published only as raw diagnostic counts.
  • Published artifacts omit merchant names, domains, raw URLs, PDP titles, snippets, screenshots, raw page text, promo codes, and private/admin evidence.

Artifacts

Artifacts are aggregate-only and include no store names, raw domains, raw URLs, raw crawl text, raw AI responses, exact promo codes, private feed/admin evidence, or merchant-identifying examples.

Correction policy

Methodology gaps, reproducible errors, or source corrections can be sent to research@storesteady.com. Corrections are published with the version history in the methodology page and report JSON.