Algolia results are from several years ago

Hi @paulagilarde

One question I have is what actually made it into the index? Are you seeing all the posts you’d expect when browsing in your Algolia.com dashboard? or is that limited as well?

We don’t have anything in place that limits by post date or really amount of posts, so the next biggest question is if the content that’s missing considered “searchable” by WordPress, also are they marked as published posts? For the searchable, that’d be when the post type is registered, it has “exclude from search” set to false.

Thanks for your response @tw2113. From what I can tell (and I’m a newbie at this) – the Angolia dashboard is also limited. The content should all be considered searchable – they are all published post. I’m working on a test site but it is a duplicate of a site that contains 12k+ posts.

Can you think of anything that might have prevented the index from being created?

• This reply was modified 1 year, 12 months ago by paulagilarde. Reason: tagging

hmm

We don’t really have a huge amount of logging in place, so we don’t have an automated spot to point to say “here’s what our queries are pulling for bulk indexing” and whatnot.

A couple things to try out. For one of the newer date posts, can you go in and click to edit the post, and just save right away, or perhaps change something minor like some punctuation. I wanna see if that ends up pushing the individual post into your algolia index.

Also, since this a test install, can you deactivate all the plugins except WP Search with Algolia and re-try a bulk indexing from the Search Page settings page at /wp-admin/admin.php?page=algolia-search-page It’s possible there’s queries elsewhere, especially if you have other plugins amending search, that are limiting results.

I re-indexed and after I got the following email from Algolia
“You’ve just reached your record plan quota.
Your application (app ID: BC90I0WF9E) has used more than 100% of the amount of records included in your plan for the period of November 28, 2022 – December 27, 2022:
10,017 records used / 10,000 record quota
You are currently blocked from uploading more records. You might need more capacity.”
What constitutes a record? Is it a post?

From their documentation: https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/in-depth/what-is-in-a-record/

Their support would be better fit to answer more detailed questions about the limits and what all is going on in this specific case.

It does sound like it’s getting a good amount of post content, but that total in the test install is more than your plan allows. I wonder if it’s going from oldest to newest, and because of the limits, it’s not able to go further, thus cutting off the newest content.

Yes, it’s getting the content but must have started from oldest to newest and ran into the limit. I wanted to confirm that the plugin wasn’t forcing a limit so thank you for confirming that it didn’t. I’ll check with Algolia to see if they can help – thanks for all your assistance!

Looking at the code that handles indexing, it looks like it queries by ID in ascending order, which means “Hello World” post would always be the first one found, if it still existed and “Sample Page” would be second, etc.

I’m also not seeing a way to amend the query arguments either, so at least as is, it’s what things are stuck with. Same thing with offset, no customization of that.

@paulagilarde did you get any sort of resolve from Algolia direct support with this? or are things kind of in the air?

@tw2113 I actually *just* got off a call with Algolia! They told me that there is a limit of 10,00 records with the free plan. The person I spoke to wasn’t very technical but did say that what I experienced was to be expected with that number of posts. We’ve decided not to pursue using Algolia right now.

Understood and makes sense on needing to pass at the moment. Hopefully in the future Algolia can re-enter the conversation as a potential solution. We hope to still be here for that.