Search returns nothing, also not all posts/pages indexed

Hello @searchiq

Sorry, we needed to wait for some other things to get completed first and we will be testing this solution over the weekend to avoid disrupting website users.

While we reset the configuration, do you know approximately how long re-indexing will take for about 600 posts/pages?

Thanks again.

@formos Sure, let us know once you check.
Re-indexing for 600 posts should take less than a minute. If the site speed is slow or the throttle rate is reduced, then it can take up to 5 min.

Excellent, that’s great to hear.

Will update once we finish the reset.

Thanks again!

Hello @searchiq

Resetting the configuration has done the trick – the search box is functioning as expected. Thank you for the support.

We have just one more thing to figure out: SearchIQ is running on our production site and we use the plugin WP Staging to run a staging site. SearchIQ is not running on the staging site. For testing purposes, how can we have both working? When we try configuring it on staging, there is the error about too many search engines.

Thanks again!

@formos Great to know it worked.
We have increased the engine count on your account for testing purposes for a week. Please index the staging site and check.

Hello @searchiq

We did a push to production, but that actually broke the search results. All results on the production site were pointing to the staging site URLs.

We don’t need to add the staging domain to the dashboard – we only ever need one active domain. We need to have all the results always be linked to the production domain. But for testing and continuity purposes we need to have the plugin installed on both domains.

How can we achieve this?

Thanks very much!

@formos No, you can’t install the plugin on both domains and create only 1 search engine on the dashboard. SearchIQ creates a separate engine for each domain. To show results from the staging site and production on respective sites, please reset configuration and input API key to index the staging site.

Hello @searchiq

Thanks for continuing to help us with this integration.

I’m not sure that having both domains on our dashboard (https://pub.searchiq.co/puser.html) is correct. That was how we ended up with links on the production domain pointing to search result links on the staging domain. Which is, of course, not ok on the production site.

Can you please advise how to definitively avoid ever having staging links appear as search results on production?

Thank you again for your help.

@formos Can you please share the links to your staging and production site?
If you are indexing separate domains (1 for staging and 1 for production), then the production results will not point to the staging domain.
You need to install SearchIQ on both the staging and production sites and re-create the engine.

@formos Also, please check if you’re not using the staging site search results page for the production site.

Hello @searchiq

The production site is: https://www.realwear.com/

The staging site is the same but “staging” instead of “www” – however, you will not be able to access this site, it is password protected.

We definitely experienced search result links pointing to staging on the production site after a push. This occured after resetting the plugin configuration and re-indexing posts/pages on both domains (the plugin is installed on both).

Lastly, we are not using the staging site search results page on production. In fact, after seeing staging results on production, I tried changing the staging site to use the production domain search results page. But this didn’t seem to do anything except possibly contribute to search being broken after the next push.

Thanks again for your help.

@formos We can see that the engine you have created is for ‘www.realwear.com’ and the results are currently showing from the production site.
Now, to index the staging site you have to reset configuration on https://staging.realwear.com, input API key, and resynchronize posts.
As you mentioned that SearchIQ is installed on both staging and production domains, you have to index both the sites separately. We can see only 1 engine on your account and the engine is not created for the staging site.

• This reply was modified 4 years, 3 months ago by SearchIQ.
• This reply was modified 4 years, 3 months ago by SearchIQ.

@searchiq

Thanks for the instructions. I have done all the steps outlined in your last answer.

The one question remains at this point: On our next push will all the search results on the production site be pointing to the staging site?

I’m worried they will be. I’ll let you know what we observe after this.

Thanks again!

Hello @searchiq

We were finally able to perform a push to the production site (we use WP Staging) and unfortunately it broke SearchIQ functionality.

All search results on the production site (example.com) were pointing to the staging site (staging.example.com) which is obviously not going to work. The bottom line seems to be that SearchIQ is not compatible with the plugin WP Staging.

I think there may be one possible workaround which would be to not have installed the SearchIQ plugin before creating the staging site using WP Staging. After creating the staging site, install SearchIQ plugin on production only. That way there would not be any references to the SearchIQ plugin on staging. Pushing from staging to production might simply ignore plugins that are installed on production but not on staging. It might merge with what already exists on production, without overwriting the production version of the SearchIQ plugin with references to the staging domain (staging.example.com), which seems to be where the issue lies.

Unfortunately, it’s too late to go that route on our site.

Thanks again for your assistance. Let me know if you have any other ideas.

• This reply was modified 4 years, 2 months ago by formos.

@formos We will check SearchIQ with the WP Staging plugin.
Do you push posts from the staging site to production using the WP Staging plugin?
If possible, can you please provide us login to your staging site so we can check and isolate the issue.