OK I figured out the problem. It was the setting for Type for Search Results in Schema Markup advanced settings. I changed that from webpage.search.results to webpage and the search results per page returned to normal (lots of posts per page). So, is this a bug and it needs to be fixed so I will change this setting back to webpage.search.results in the future or I can safely keep the Type for Search Results setting as webpage without this negatively affecting the schema markup ? thank you
The https://schema.org/SearchResultsPage markup is considered an archive type by WPSSO and the plugin requests the list of post objects from WordPress – there is no difference between the request that WPSSO makes for search results and other archive types pages (categories, tags, etc.). All these requests are working as expected in test environment and all customers (I’ve never seen a ticket about this), and no changes to this code has taken place in a long time. That doesn’t mean that the bug is not in WPSSO, but it’s unlikely.
What is most likely is that WPSSO is triggering an existing bug in another plugin or your theme. If you don’t have a plugin manipulating / formatting search results, then it’s most likely your theme.
I would suggest defining WP_DEBUG as true (see here https://wpsso.com/docs/plugins/wpsso/installation/troubleshooting-guide/) and activating the Query Monitor plugin as suggested. This will likely log an error message in your debug.log file when you load a search results page. If you don’t understand the error message, copy-paste it here and I (or someone else) will likely be able to offer more guidance.
js.
