Randy Hodge said:Hi Luke,
The default page that is requested when creating a search index is the page you have set up to display the content. This is so that when the user clicks on the item in the search results list the item will redirect to that page which has the proper widget for displaying it. It is not a dump page for creating the index.
For example, if you have News and Blogs, you have a page to display News and one to display Blog Posts. If you then create a search index for News and Blogs, you point it to the News page for News and the Blogs page for Blogs. This is simply the landing page for that content. You do not need to create a new page just for the index.
Hi Randy, thank you for the response.
It is starting to make a little more sense but I'm still getting 404s from search results when I try to index posts from different content categories.
Explanation: the search index I created targets a specific blog. We want to provide users with a simple way to search across all posts within it. The posts within that blog are categorized each into one of a dozen different content categories.
On the front end, these posts are not displayed in conventional blog archive format (i.e., post titles & excerpts from all categories, ordered by date descending) but rather are accessed from custom landing pages, each with a group widgets that list the N most recent entries from date X from respective categories A, B and C etc.
My goal is to search across all post categories in that blog, but I don't have a front end page that displays posts from all of its categories, and thus if I point the index to some parent page upstream of the posts-by-category pages, my search results all click through to 404 errors.
As I just mentioned each category does have a front end page with a more conventional archive list of posts in paginated list format (posts-by-category style), and I've discovered that if I point the search index to one of those front end pages it seems to behave predictably from start to finish.
My problem is that I want one search to parse all categories, rather than construct a dozen different search indexes and corresponding experiences (one for each category.)
Do I need to build a front end page that feeds from all categories, or is there a simpler solution I'm missing?
Appreciate the insight!