Posts aren’t visible in Google Mobile-Friendly Test

I suppose my initial question is if you’re using Algolia to power your product displays, as well as potentially for user-submitted search queries.

I know Algolia has the ability to power browsing/landing page functionality, but that’s a section/topic that we don’t cover with the plugin here, as we focus on the search aspect where applicable.

Hi Michael,

I understand. So there is no easy way to switch from POST to GET, right?

Not that I’m aware of, since it needs a queried term to be posted aka searched for, for it to return results, at least for how our plugin here works. We’re meant to be used to take over the search queries and utilize indexed data instead of local WP database data.

Still not quite sure how you have your setup at the moment, as it sounds like it’s expected to make search results ready to be indexed by Google in some way, when there’s no queried for term yet.

Unfortunately I’m not the person who did the customization on our site.

But as I see it, we’re using a search request to show the result as a category page.
In our plugin “Search Page” setting the option “Use Algolia with Instantsearch.js” is active.

I guess that’s why it doesn’t work right now. Google can’t see these results.

It’s just a huge problem for me right now because we’re loosing our visibility in the SERPs ??

Understood on it being a problem and losing SERPs and everything, I also know that literally just this afternoon I’ve been working on a client project that is using Algolia and also WooCommerce, and I’ve been fighting getting the product category archives to be algolia based. I’ve been tinkering a lot with setting a query to be run upon load time by Algolia, instead of having to manually trigger a search, all based on the queried product category.

Fun times, and interesting timing coincidence, if I’m following everything right.

You do follow everything right ??
Very interesting coincidence indeed.

If you stumble across a solution, I would be very grateful for a hint ??

At least thus far, I’ve been working with https://www.algolia.com/doc/api-reference/widgets/configure/js/

Thank you Michael, I tried to understand it but unfortunately it’s out of my league ??

Me again, is there any way to “hire” you for fixing our category site based on your plugin and your work for the other client?

I had a discussion with our seo consultant and we really really need to fix the problem or deactivate the plugin for the category pages. But that would be very sad.

If there’s an option, please let me know how I can contact you for further details.

Best I can offer on that part would be reaching out over at https://webdevstudios.com/contact/ and starting a discussion there. Definitely won’t hurt to include this forum thread here so that we retain the context and whatnot.

Done, thank you very much so far!

Has someone else a similar problem and/or a solution for that? I’m still trying to fix that ??

• This reply was modified 2 years, 8 months ago by pixelguy.

No one else has had the issue that I can recall, at least in my time involved with the plugin.

OK, the question was more for the community and not directly for you ??
But thank you.

For what it’s worth, based on my recent experiences with Algolia and WooCommerce, I’m working on a blog post to hopefully better explain integrations and code examples of how, etc. It’s in the works.