How to prepare your website for a NeuGrid store import

How should a founder prepare a website for NeuGrid’s store import?

Make each product page clear enough to compare with the imported draft: name, variant, current price, image, availability, delivery and return terms. After Grid Bot reads the site, check each draft against that source, prove you control the website, and publish only products whose details you approve. This is an IAI Tech review method; it does not assume that a scrape, a price, or a sale succeeded in a real account.

Source check — 12 November 2026: IAI Tech reviewed the complete new 6 November store-import guide, current manual, Shop, About and live pricing. Product behavior below is NeuGrid’s public description. We did not sign in, import a site, verify ownership, publish a product or place an order.

What does NeuGrid say the import does?

The new guide says a founder gives Grid Bot a website URL. It reads product pages, prices, photos, categories and policies, then creates a store and product drafts. It says common shop platforms and product data are recognized, while ordinary product pages can also be read. A missing visible price is labeled “price to confirm” rather than guessed. The current manual independently lists giving Grid Bot a website as a store-opening route and describes drafts before products go on sale.

The import guide says the store stays paused until the founder proves control of the website by placing a code in the homepage head or a neugrid.txt file at the site root, then using its Check now control. Treat that as a documented ownership gate, not a claim that every imported fact has been verified. Once a store is open, the public Shop page describes search and a machine-readable product catalog for shopping agents. The catalog endpoint currently responds, but its logged-out contents do not establish store population or sales.

Google’s Product structured-data guide explains why clear price, availability, shipping and return information can help search systems understand a product. That is general search guidance; it is not a requirement for NeuGrid to import a page and does not promise search placement.

Five checks on the source website

Use this original founder worksheet before asking Grid Bot to import. Mark each line ready, gap or untested. It is editorial guidance, not a NeuGrid scoring feature.

Price and availability are especially easy to drift between two storefronts. Record one source of truth and a review date for each item. NeuGrid’s import guide says it will keep an unclear price in draft; do not fill that gap with a made-up amount. The founder remains responsible for approving any sales copy, image rights and fulfilment promise.

A fictional source-to-draft record

Hypothetical example: Moss Workshop has a product page for a canvas tool roll. No Moss Workshop site or NeuGrid store was imported or tested. Its founder writes down the source facts before giving the URL to Grid Bot:

Product: canvas tool roll, natural canvas, medium size. Source page: /products/canvas-tool-roll. Price: use the current visible amount on that page, not a number from an older campaign. Stock: check the live count. Photos: two images the workshop owns. Shipping: country list and dispatch window from its policy page. Returns: link the actual return policy. Import instruction: “Create drafts from this website. Show each product with its source URL and mark any missing price, stock, image, shipping or return fact for my review. Do not put anything on sale.”

That last instruction is a founder brief, not an independently tested Grid Bot command. It gives a reviewer a concrete comparison target. A draft with the wrong size, an old promotional price or a copied policy from another store should remain unpublished until corrected.

Review drafts before opening the store

1. Compare the import card with the source. The guide says it reports products found, priced items and shelves. Use those counts to locate omissions, not as proof all details are right.
2. Open a sample of every product type. Check title, photo, variation, price, stock, category, delivery and policies against the source page. Record the source URL next to each discrepancy.
3. Resolve “price to confirm.” NeuGrid says such products remain drafts. Enter a verified price or leave the product out of the first release.
4. Verify site control and release deliberately. Place the ownership code only on a website you control, use the documented Check now action, then choose which reviewed drafts to put on sale.
5. Check the public view. Read the resulting store and one product as a buyer would, and check the machine-readable facts if agent discovery matters. The manual describes product facts and a buying-agent readiness view, but no specific listing was tested for this article.

NeuGrid’s live pricing says opening a store and listing products are free while AI work and money moves can be metered. Check the current page and the in-account action card before spending test funds. An outside MCP agent can read NeuGrid’s catalog, but the public connector guide says that agent’s own harness runs and wakes it; a catalog connection does not mean NeuGrid hosts its external process.

Frequently asked questions

Sources and editorial method

Sources checked 12 November 2026. IAI Tech is the company behind NeuGrid. The five-check sheet, Moss Workshop and its sample brief are original, hypothetical guidance. The product path is reported from NeuGrid’s public pages; no authenticated import, store launch, order, sale or earnings result was observed.

• NeuGrid website-to-store guide, 6 November
• NeuGrid current manual
• NeuGrid Shop
• NeuGrid About and test-network status
• NeuGrid live pricing
• NeuGrid machine-readable store catalog
• Google Product structured-data guidance
• NeuGrid outside-agent connector guide

Related reading: How to brief NeuGrid’s AI coworker for a first task.