My approach is not for an SPA, and the examples you gave of .com/es/playas-de-arena/espana versus .com/beaches/en/sandy-beaches/spain are not examples of URLs that are possible via an SPA in Bubble because when you alter the index pages URL to append a path it makes the url into .com/index
Sure, if you want to have the different languages for the page name, but that is not necessary, and since it would cause an issue and is not necessary it is avoided to achieve the desired result of having multiple languages on the same page with great on page SEO for each language and each content type. Google does not (as far as I can tell after reading through most of Google pages related to SEO) penalize you for not changing the entire URL into the other language. And in fact most major sites do not do that anyway.
Check here for some examples of top multi language sites, go to a page, change the language and notice how most likely are not changing the page name in the URL to match the language.
Not sure if you were under the impression based on research that you NEEDED to change the page name to reflect the language in order to get good on page SEO scores by Google or just based on an assumption, but for me, when researching, I look to sources (ie: Google) for giving me the playbook of ‘what needs to be done’ then I look at the ‘big players’ on the web (or in the specific industry) and I go through their sites an analyze what they are doing.
Yeah, that is based on your use case, and attempts at making it work. It seems like you are attempting to do it in an SPA, so of course you are going to end up with a mess like that. If you were doing it on a specific page, you’d likely need to revisit how you structure your data or the pages to make it work properly. Most of the time, apps do not need much more than category and subcategory.
No, I don’t agree as that is what I have done in my app to get the desired results. I use the formatted as text operator to create ‘in-line’ conditions…but yes, if I had that mess of conditions in your example image, it would be cumbersome, but not impossible.
I avoid using the filtered operator through techniques that can be found on the forum. When applied correctly it speeds up the search tremendously and allows for better UX and faster performance. One of those techniques is to use text instead of a list field, as I’d imagine the only reason anybody is really using a :filtered operator is to match a list of filters selected to a list field on the data, which doesn’t need to be the only way to achieve the same desired result for a feature of allowing a user to select multiple filters to match against a list of filters on the data entries.
I live in Thailand, there are no Bubble servers here and this does not create much of an issue for me, which might be because I am building my app optimally (at least I believe I am and the results I’m seeing would indicate I am).
In the end, it is fine if you want to disagree conceptually, it is not going to alter my approach that does work and is working as the screen shots from Google tests indicate.