Hello,
How does the Country/Region field affect search functionality, if at all, when that field is NOT set as a searchable field? I’m curious because it seems that the Country/Region field is required while uploading data for most entity types, including things like FAQs that don’t have locations.
To provide added context, I have a client who is going to have a Resources vertical with case studies, blog posts, white papers, etc. For a few of their Resources, they filled in the Country/Region field with more than one answer, e.g., “US/UK/Australia”, and I want to understand the impact of choosing just one of those three options to use for that field.
Thanks!
DJ
Hi DJ,
Great question - the Country/ Region field is important only for location search support by country. By that we mean that if your entity has a Location or Address, and you want builtin.location to be searchable, then it will be important that the Country/Region on the Entity is correct and that same Country is included under “Country Restrictions” in the Search Config UI. However, if not then you don’t need to be concerned with the Country code for those entities.
You can see more information about the differences between Localizations and Country Restrictions at the bottom of this module here.
Let us know if you have any other questions!
Best,
Alyssa
1 Like