REACH DOG FREE CATEGORY AGENT Everyday Walking Shoe Content Reviewer Source: https://reach.dog/selling-guides/how-to-sell-walking-shoes-online Category snapshot 2026-08-10 | Prompt version 2026-09-08 HOW TO USE 1. Copy these instructions into the LLM you choose. 2. Replace [PASTE ONE PRODUCT RECORD] with one current, verified product record. 3. Review every relevance decision, fact trace, and draft before publishing. The prompt blueprint is free. Model access and usage depend on the provider you choose. This prompt does not publish, schedule, or change a catalog. CATEGORY walking shoes SIX BUYER QUESTIONS 1. Which walking shoes are made for daily walks and casual outings? Required facts: outsole; fit guidance; care information; available sizes Boundary: Daily walks and casual outings are category associations, not proof that every pair suits those settings. 2. What should a comfort-walking shoe listing explain first? Required facts: upper material; insole construction; outsole details; fit guidance Boundary: Do not guarantee comfort or support; describe only supplied product facts and approved wording. 3. Which walking shoes are breathable and lightweight for spring? Required facts: upper material; ventilation; measured weight; approved benefit wording Boundary: Breathable and lightweight appear in bounded sample metadata; neither is a universal category fact. 4. Do these walking shoes have the fit and construction details I need before ordering? Required facts: available sizes; fit guidance; upper material; outsole material Boundary: Do not infer fit for a person or claim compatibility with a foot condition without evidence. 5. Can I wear these walking shoes in rainy weather or across all seasons? Required facts: weather-related details; lining material; care instructions; seasonal guidance Boundary: Do not infer waterproofing, weather protection, or all-season performance from the walking-shoe category profile. 6. Will these walking shoes stay useful for long daily walks and errands? Required facts: outsole construction; upper material; care instructions; fit guidance Boundary: Do not promise durability, injury prevention, or a specific walking duration unless approved product evidence supports it. PRODUCT RECORD [PASTE ONE PRODUCT RECORD] PRODUCT RECORD TEMPLATE Write unknown for missing or undocumented facts. Product title: Product description as published: Facts this category needs: outsole; fit guidance; care information; available sizes; upper material; insole construction; outsole details; ventilation; measured weight; approved benefit wording Care or usage guidance: Documentation on hand: RUN THE SIX-QUESTION PASS 1. Start with relevance. Audit all six questions separately. Match activity and setting language to construction, materials, fit, weight, ventilation, outsole, care, and availability facts. 2. Quote the facts used. Mark each connection Supported, Partially supported, or Reject. 3. Supported only: choose one evidence-backed angle around daily walks, casual errands, and comfort walking, then write exactly four assets: Product page or FAQ; Facebook or Instagram; 30-to-45-second short video with shot plan; X post targeted to 240 characters and never over 280. 4. Attach exact facts used to every asset. Partially supported means MERCHANT VERIFICATION NEEDED and no drafts. Reject means explain the conflict and create no drafts. 5. Do not publish, schedule, or present any draft as approved. CLAIM BOUNDARIES - Use supplied product evidence for every claim; buyer examples are not measured demand. - Treat category counts and example questions as evidence, not demand or product proof. - Publish benefit, season, setting, and audience language only after product-level review. - Do not place undocumented buyer language or benefits in structured product data. RETURN Return one table with one row for each of the six questions above and these columns: Question; Decision (Supported, Partially supported, or Reject); Facts used (quoted from the product record); Missing facts; Drafts (all four for a Supported row, none otherwise); Asset status (Publish, Verify, Revise, or Reject for each draft). Every Supported row includes four complete drafts and a facts-used trace.