gaash.ai

Local & Industries · 8 min read · September 26, 2026 · , gaash.ai

In stock near me: stating availability, pickup and the way to check

"In stock near me" asks two things at once: whether a store close by has the item, and whether the shopper can have it today. A store answers the first with the lines it always carries, a way to check one item and what "in stock" means on its site, and the second with pickup terms and a page for each location.

What an in-stock question asks of a store's pages

Take "[brand] trail shoes in a size 10 in stock near me today". It names an item down to the size, a place, a time and, left unsaid, an action: the shopper wants to walk in, try the pair on and leave with it, or reserve it and collect it on the way home. Each of those is something your store either states on a page or leaves to guesswork.

With web search on, an AI assistant reads a handful of pages before it replies. A sentence such as "we keep [line] in sizes [range] all year; call [number] to check your size" gives an answer a fact it can repeat. A stock count that a script writes into the page after it loads gives a text fetch much less: the assistants' crawler documentation says nothing about running scripts, and Google renders JavaScript only as a separate, deferred step.

Our own crawl counted how many small business sites are built that way. In our audit of 9,483 small business websites, fetched by an AI crawler that ran no JavaScript in late August and early September 2026, 3.0% rendered their content only in JavaScript and 2.1% kept their real content in a PDF. Both figures are across all 40 trades; we publish no retail-only cut.

Four kinds of availability, and where each is stated

"In stock" covers more than one fact. Some of what a store has is true all year, some is true this hour, some can be ordered in, and some can be tried before buying. Each belongs on a different page and changes at a different pace, so write them apart.

The kinds of availability a store can state, how fast each changes and where it goes. Brackets mark the store's own figures.
KindWhat the store statesHow often it changesWhere it goes
Always carriedThe lines and sizes kept all year, by category: "we keep [line] in sizes [range]"Rarely; date the page when it doesCategory pages and the brands page
On the shelf nowThe stock line for one item at one store, with the time of the count: "[n] at [store], counted [time]"By the hour; say how often the count updatesThe product page, as text in the HTML
Can be ordered inThe lines you can get and how long it takes: "order-in from [brand], about [n] days"With each supplier's termsCategory pages and the stock and pickup page
Can be triedDemo models, test rides or fitting stock: "[line] demo pairs in sizes [range]"With the seasonThe category page or the service page

The first row is true on any day an answer might be written, which is why it comes first. The second is only as good as its update. A count that still reads "in stock" in the evening for an item that sold at noon is a fact an answer can repeat wrongly the next morning, so a store that cannot keep a count current does better to publish the first and third rows and a way to check.

How a shopper checks one item, written down

On the stock and pickup page, and in a line on every product page, say how a shopper can check an item before making the trip: the stock line on the page if you keep one, a phone number and the hours it is answered, a message channel and how fast you reply, and what the staff do when asked ("we check the shelf and hold the item for [n] hours").

Then say what "in stock" means on your site. If the count covers two locations, or includes items on order, a shopper who reads "in stock" in an answer can arrive at the wrong store or on the wrong day. Write it out once, near the count: "In stock means on the shelf at the store named beside it, counted [how often]."

In the product page's Product markup, an Offer carries the availability. schema.org's values include InStock, InStoreOnly, which it defines as available "only at physical locations", LimitedAvailability and Discontinued. The Offer's availableAtOrFrom property names "the place(s) from which the offer can be obtained (e.g. store locations)", so an offer can point at the store's own node. The structured data repeats the page and says nothing the page does not, and Google's structured data guidelines ask for it to be up to date, which for a stock line means as current as the count beside it.

Reserve and collect, stated as terms

A shopper who asks whether they can pick something up today wants the terms before they leave the house. Put them on the stock and pickup page and repeat them in the reservation confirmation, in the same words:

  • How to reserve: online, by phone or by message, and whether payment is taken at once or at pickup.
  • How long an item is held: [n] days, and what happens after that, as your terms say.
  • The same-day cutoff: reservations made before [time] are ready that day; later ones the next day.
  • Where to collect: the counter, a pickup point at the door, or the curb, and the times the counter is staffed if they differ from the store's hours.
  • What to bring: the order number, and ID where your terms ask for it.
  • Who can collect: the buyer only, or anyone with the order number.

An offer that can be collected can say so in markup as well: schema.org's availableDeliveryMethod takes OnSitePickup, defined as a method "in which an item is collected on site, e.g. in a store or at a box office". Cancellations, refunds on reservations and deposits follow your own terms. The rules on what those terms must allow differ between countries, states and provinces, so state yours plainly and have counsel check them.

The location page an in-stock answer can point to

Stock and pickup are facts of a place, so each location needs a page of its own. It states the address, the hours for each day and holiday hours posted ahead, the categories and lines that store keeps and the ones it can get in, the pickup counter and its terms, the services on site, and directions a shopper can follow. Mark it up as the store's own node, typed as its LocalBusiness subtype, such as BikeStore or BookStore. The stock line on each product page names the location it counts, so that "in stock at [store]" can only mean one place.

A location page is worth writing for what differs from the next one: its stock focus, its services, its hours. A page for a town where you have no store, or a copy of another location's page with the town changed, is what Google's spam policies call doorway abuse, since it aims at a place in order to send the reader somewhere else. The article on businesses with several locations covers the listings and markup for more than one store, and the guide for retail stores puts this page in the order of the rest.

What Google says about Merchant Center and a store's stock

In its section on local business and ecommerce details, Google's guide to generative AI search says Merchant Center and Business Profiles help product and local details appear. Google's page on AI features puts checking that both are up to date among its practices.

Neither page describes how in-store stock reaches Merchant Center, and this article does not either; that belongs to Merchant Center's own help pages, and the route is Google's to state. What is yours in any case is agreement. If your product data goes to Merchant Center, the price and the availability there should match the product page and the location page on the same day, because a feed that disagrees with the page is a second answer to one question.

The Business Profile carries your hours as well. Keep its regular hours, and its special hours for holidays, equal to the location page and changed on the same day; the same-day change routine sets out how, for hours, holidays and the brands you carry.

Common questions

We don't show stock online at all. What can we still say?

The facts that hold between deliveries. State the lines and sizes you keep all year, what you can order in and how long that takes, how to check one item by phone or message and how quickly you answer, and your pickup terms. None of it needs a live count, and none of it goes stale when the last pair on the shelf sells.

Should product pages show exact stock counts?

Only if the count is kept current and the page says when it was taken. "[n] at [store], counted [time]" is a fact a shopper can weigh. A count that lags the shelf by a day is worse than none, because an answer can repeat it. If you cannot keep it current, show whether the store keeps the item and give a way to check.

How long should we hold a reserved item?

That is your decision; what matters is that the number is the same everywhere it appears. Put it on the stock and pickup page, in the confirmation message and on the sign at the counter, and say what happens when the time runs out. A shopper told "held for [n] days" by an answer should hear the same number at the register.

A shopper was told we had an item we sold out of weeks ago. Where did that come from?

Look first at your own copies: the product page's stock line and its time, any feed you send, and any marketplace or directory listing that shows stock. One of them may still say "in stock". Checking answers against the stock list shows how to trace a wrong fact to the page that states it.

Sources

The two audit figures are this site's own, sample-wide across 40 trades, with no retail-only cut. What schema.org's Offer values mean is quoted from schema.org; what Google says about Merchant Center, rendering and doorway pages is from its own pages, linked where used.

Sources: our audit of 9,483 small-business sites, with its method · schema.org, Offer · Google, JavaScript SEO basics · Google, general structured data guidelines · Google Search Central, spam policies · Google Search Central, optimizing for generative AI search · Google Search Central, AI features and your website

All articles