Magento and Adobe Commerce and furniture retailer
Finding the number the crawler actually read
The most important number on a furniture site is the wait, and on Magento it is usually not a page. It is a CMS block, dropped onto product pages by a widget rule, printed inside a page that is itself served from cache. There is nothing to point an assistant at, nothing to check a version against, and two separate layers between editing the figure and anything outside the shop being able to read the new one.
Why this pairing is its own job
The Magento and Adobe Commerce install guide covers the tag, and the furniture retailer guide covers what the assistant has to know. What follows is the part that belongs to neither.
- A CMS block has no address. You can edit it, you can place it, and you cannot link to it, which means it cannot be indexed as a document in its own right and can only be read wherever it happens to be printed.
- Product pages are served from the full page cache, so what a crawler receives is whatever the cache is holding. Update the block, skip the flush, and the figure that gets learned is the old one, which for a lead time is not a cosmetic problem: a quoted wait becomes part of what the customer agreed to.
- The same page often carries the number twice. A block says one range and an attribute row in the specification table says another, because they were set up by different people at different times, and nothing on the page reconciles them.
- Clearance and ex display usually run as their own store view with genuinely different terms, since a piece sold as seen carries a different position on returns and guarantee from the same model built to order. Those two sets of terms must not end up in one index.
What changes about the install here
<script src="https://cdn.askably.xyz/w.js" data-key="pk_live_YOUR_KEY" defer></script>The tag is the same one on the Magento and Adobe Commerce guide. Everything below is about where it goes on a furniture retailer site specifically.
Flush, then crawl, in that order
There are two caches to think about, and only one of them is Magento's. The platform's full page cache decides what any visitor gets, and a content network in front of it can hold pages for longer still. A crawler is just another visitor as far as both are concerned.
So the sequence after changing a lead time is: save the block, flush the Magento cache, flush anything in front of it, load a product page in a private window and confirm the new figure is there, and only then recrawl. Doing it in any other order indexes the number you were trying to replace.
This is worth writing down next to whoever updates the lead times, because it will be a different person from whoever set the assistant up, and the failure it produces is silent.
Give the lead time an address of its own
Create a CMS page holding the lead times for every range, with the date they were reviewed at the top, and have the block on the product page link to it. The block keeps doing its job in the layout, and the page gives you one place to edit and the assistant one thing to cite.
The citation is the part that pays off. When somebody quotes a wait back at you, you can see which document the answer came from and when it was last touched, which is impossible when the only copy of the number lives inside a block printed on four hundred pages.
Keep the clearance storefront separate
Design Configuration is scoped, so an outlet or ex display storefront can take its own key without any extra work. Use that, because the terms genuinely differ: a sold as seen piece has a different returns and guarantee position from a made to order one, and mixing the two documents produces an assistant that offers outlet terms on a full price order.
It also stops the lead time confusion spreading, since an ex display item has no lead time at all and the answer to how long is the wait on that storefront is a different sentence entirely.
Where the answerable material lives
| Lead times as a page, with a reviewed date | Every range, stated as an honest range in weeks including the slow end, with the date the figures were checked printed at the top. One document, one address, one place to edit, and something you can look at in six weeks to decide whether the assistant is still quoting a figure you stand behind. |
|---|---|
| What the quoted wait is measured to | Whether the number is to dispatch, to arrival in the country, or to the delivery slot in the customer's home. This single ambiguity produces more furniture complaints than any other, and stating it explicitly costs one sentence in the same document as the figures. |
| Deposit and balance terms | What the deposit secures, when the balance falls due, and what a cancellation costs at each stage of production. Customers ask about cancelling once the wait starts feeling long, and this is the answer that has real money attached to it. |
| Clearance and ex display terms, kept apart | What sold as seen means in practice, what still applies whatever the label says, and what does not transfer from the main range. Its own document, indexed only for the storefront it belongs to. |
The first thing to get right
Move the lead times onto a CMS page with its own address and have the product page block link to it, then flush and recrawl.
It converts the most volatile number in the shop from something painted onto four hundred cached pages into a single document you can edit, date and see cited. Every other lead time problem on this platform, the stale cache, the two figures disagreeing, the range nobody remembers updating, becomes visible the moment there is one page to look at.
The failure that belongs to this combination
Two lead times on one page, and it picks one
The block at the top of the product page says ten to twelve weeks. The attribute row down in the specification table says eight, because it was filled in when the range launched and nobody has revisited it since. Both are on the page, both were crawled, and neither is labelled as the authoritative one.
A customer asks how long the wait is, gets eight weeks, and cites your own product page back at you in week nine. The answer was sourced, the source was real, and the shop is now arguing with its own website about a term of the sale.
Look for it by asking the assistant the lead time on three ranges and comparing the answers against the block, then go and empty whichever field is wrong rather than correcting it. A stale figure that has been deleted cannot be matched. A stale figure that has been corrected can drift again.
Before you go live
- The origin the page is served from has to be on the allowlist for that assistant, or nothing renders and the browser console says which origin was refused. An apex domain and its www are two different origins to a browser, so list both, along with any staging or preview host you want it to work on.
- Open the site as a visitor would, on the pages a furniture retailer visitor actually lands on, and ask it something only your own material could answer. A widget that renders is not the same as a widget that has read anything.
Questions
- We flushed the cache and it still quotes the old figure.
- Flushing changes what visitors get. It does not change what was already learned, because the index holds what the crawl read at the time it ran. Flush first, confirm the new number is on a freshly loaded page, then recrawl. The order is what makes it stick.
- Should clearance run on its own assistant?
- Yes, where it runs on its own store view. Ex display and made to order carry different positions on returns and guarantee, and one index containing both will offer clearance terms to a customer who has just paid full price for something being built for them.
- Can it tell somebody where their order is in production?
- No. It reads pages and documents and has no sight of a production schedule, so the honest reply names the published range and offers a person. It will take a name, an email and a message, and that arrives with whoever can open the order and give a real date.
Keep reading
- Installing on Magento and Adobe CommerceUse the Miscellaneous HTML field in Design Configuration rather than a theme file, then flush the full page cache or nothing changes.
- Everything for a furniture retailerLead times, delivery access and assembly dominate furniture enquiries. What an assistant answers well, and where it must take a name.
- One assistant per store view, because the rights differConsumer rights differ by market and Magento already splits your storefronts by store view. Give each one its own assistant and its own pages.
- Options that change the order, and the pages nobody links toFabric choices are modifiers, dimensions sit in custom fields, and the pages that answer a furniture question are orphaned in the footer.
- Where the answers stop on a Shopify furniture storeDelivery surcharges are resolved at checkout, where the theme tag cannot reach, and your dimension files are linked from an address that is not your shop.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.