FAQ
What is SKU.md?
SKU.md 1.0.0 is an experimental community proposal for merchant-published Markdown catalog entry points and optional source-linked product details. It is not an official standard.
Who reads SKU.md directly?
Supported agents, search-engine crawlers, and other automated readers are the direct readers. Merchants publish, review, and maintain the human-readable Markdown; shoppers benefit indirectly through tools using it. Human readability supports maintenance, not a shopper-facing document. Publishing does not mean any tool adopts, indexes, or cites it by default, and source checks do not certify accuracy.
Will AI automatically read my SKU.md file?
Only tools that support SKU.md can use its discovery and reading rules. Publishing does not mean any agent, search engine or platform will automatically adopt, index or cite it.
How do I start using SKU.md?
Create a catalog draft from your public store homepage. Review the merchant name, summary, version, Website and Catalog links, then download it and publish it on your store. Check the published URL afterwards. Product-detail documents are optional.
Is product knowledge required?
No. Publish the root file first. Add a product knowledge document later only when each fact has one or more absolute HTTPS Source links.
Where do price, inventory, shipping, and checkout belong?
They remain in the current product page, feed, catalog, or transaction protocol. SKU.md does not carry live commerce state.
What do document, published, and graph validation mean?
Document checks one file; published checks its live HTTP contract; graph checks same-origin links, root-to-product relationships, sources, redirects, and final URLs.
Does publishing SKU.md improve ranking, citation, or sales?
No outcome is promised. The file can make official catalog discovery and sourced facts easier to inspect, but search engines, agents, and platforms decide how they use it.