Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Handling hyperlocal product SEO

         

nikhilrajr

9:52 pm on Jun 2, 2020 (gmt 0)

10+ Year Member Top Contributors Of The Month



Online grocery store has different catalog in City A and B. Currently the bot request goes to city A. There are no internal links to products that exist in city B when you browse city A. As this will provide a bad user experience. When you request city B products from city A, they will appear as "Not available".

How will I ensure Googlebot is able to crawl all these products?

Products in city B are added in the XML sitemap. These products when requested shows Not Available in place of Add to Cart button. Because there are zero internal links from the default city A, these city B pages rank rarely in search. Also these pages are getting removed from the index. My theory is whenever bot requests city B product it's always Not available, there's no change in the page, no internal links and is getting treated as soft 404.

I am thinking of creating a dummy city C for bot requests with a union of city A and B products. This will solve for the internal links issue.

But in this City C, calculating availability is going to be tough. So my solution is to show all products in City C as in stock for bot requests. Curious to know your thoughts on this. Users will continue to see in-stock, out of stock, not available status based on the location of the request.

Also, does out of stock products get down ranked in Google search?

Robert Charlton

8:51 am on Jun 4, 2020 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



nikhilrajr, are you talking about Google Shopping, or about organic search?

It sounds like you're talking about organic search, but that you are wanting the control of Google Shopping. My comments below are for organic search, where, last time I looked, you cannot tag products as in or out of stock in a way that would be seen by Googlebot.

Organic search results simply can't give you the control of a Google Shopping feed, at least not as you've described.

Re organic... just some general notes, not specifically addressing all details of your plan, but I hope enough of them to give you some ideas... Again, this is for organic, not for Shopping results.

In my experience, trying to control what appears in Google's organic index with XML sitemaps would be a real crapshoot, as you have no control about how or when Google will rank or index you.

Additionally, Google's results aren't fresh enough for search to show what's in and out of stock on a geo-location basis and at a given point in time.

Systems that depend on IP and a periodic query to a central inventory database (which is the way some chains handle this), are, in my experience, often inadequate for the following reasons...

- an IP used to determine search location can't determine what store in, say, a metro area the searcher might want to shop at.
- periodic inventories depend on how often the inventories are made. Once-a-day, eg, which is how many ecommerce chains with retail outlets do it, may well not be frequent enough if your stocks are low.

On retail ecommerce, an often-used solution would be to have the customer (once on the site) enter a zip code and a radius, and then manually check stores in the results presented... and you'd use whatever inventory control system you've chosen when the customer asks about availability. .

Long ago, I worked with a retail food operation where everything was bar-coded, including even local deliveries, so information provided to users could be very current. Note, though, that this does not interact with organic search, and is a very expensive system to set up.

In a sense, your plan C, a database including both locations A & B, is closest to the above, though it sounds unlikely that you use barcoding... and organic search is not affected. But at least your largest possible inventory is what the user is querying (not on Google, but on your site).

If you have really different multiple catalogs, for organic search, you might consider separate sites that incorporate location names. You'd still have the in and out of stock situation, but the user-experience is likely to be better. Some large chains do this, but more on the level of what appliances they stock... not on grocery inventory.

I'd also say it would be a bad user experience for users not to see your inventory situation until they are checking out.

Note that we have a separate subforum for Google Shopping here [webmasterworld.com...]

nikhilrajr

8:32 pm on Jun 4, 2020 (gmt 0)

10+ Year Member Top Contributors Of The Month



Thank you for this. I found the bar-coded situation really interesting.

Yes, I am talking about Google Organic Search and not Shopping.

The catalog is not completely different. For example, fruits &vegetables are available in all the stores. The difference comes in certain FMCG product brands which are famous in that location. For example, Cheetos, certain beverage brands, local Ice-cream brands is stocked only in City B.

And plan C, a database including both locations A & B, is only for bot requests. That way these products will end up in the index and can rank in Google organic search.

A user will never see City C. He will be diverted to City A or B based on his location. And users will continue to see the stock availability on the website.

The website has catalog for around 30 cities and around 300 Hubs. So calculating availability for this Global city I am planning for bot requests is going to be a huge engineering challenge. The easiest option is to show products as always in-stock for bot requests.