Two Answers Front-Ends Sharing a Backend

Search
1

Hey all!

Wanted to validate an approach I have before diving into development here.

I have a client that wants to take their main Answers experience to a sub-property, but only the locations vertical. They don’t want any of the other 4 verticals to appear. My intuition is to create a second answers front-end that has only 1 vertical, but I had some questions about the execution:

  1. Would I simply configure the index.html file to be vertical-specific rather than universal in this case?
  2. Will having two front-ends with the same backend have negative effects on their analytics?
  3. Are there any other concerns or flags I should raise to the client about doing this before I move forward?

Thanks!

2

Hey @Jack_Perales thanks for reaching out and sharing this use case.

Your approach makes sense to me. You can build a vertical-only page (using index.json and index.html as you noted) on the frontend using your existing, Universal search backend. Note that all of your in-platform Analytics will be grouped together and tied to the same backend config. I wouldn’t call this a negative effect rather just an implication to be aware of.

Best,
Sam

3

Thanks Sam! Appreciate the second opinion. I’ll go ahead with this solution and see how it works out.