A trivial question that needs discussion - which is better, a complex catalog component or 1000 index pages with a section list + catalog section?

Question

1C-Bitrix

Hello!
When setting up the directory structure, I thought about its contents many times and now the question arises.
This is my first site, and when I first started, I was told by one developer, who has correspondingly more experience, that it is best to make a catalog section in the index page and place subsections corresponding to this section there, as I understand it, he meant SEO. Internal optimization is good, but I don’t understand what is the point here, I wanted to know if this is really so? That is, I have a section - Samara (city) and in it subsections corresponding to it. Should I make this section on the index page and use catalog section list + catalog section and smart filter in it? or if nesting is needed, for example, not 1 , but 3, do the same index subsections with the same structure.
Or does all this successfully replace the complex component?
I also want to know about the load on the server:
In the case of a large number of index pages, in reality, the response issued by the server in each specific case will be less, that is, a smaller number of products will be processed in each specific case, that is, I think such query segmentation to the directory should be justified to some extent in terms of performance, and what about indexing, but for me this is just a theory.
On the other hand, if there are 20,000 index pages on the site, won't this load the server's work so that no optimization described above will play a role?
That is, what is better, to use a complex component or to split the catalog into separate parts, placing sections of the infoblock in different index folders?
Thanks

Answer 1

In my opinion, you choose between a bad and a terrible decision.
At the same time, it is not very clear how 20,000 index pages can "load the system". Why does it have to be worse / harder from the technical side?
20,000 index pages will load you up - it will turn into a monkey's work to maintain this. It is not at all clear why you are going to make a separate index page for each section. Why not make it one for all sections?
False dichotomy here. Why do you think you have a choice between a complex component and your own index page for each section?
Make three files in the directory - index, section, and detail - and place the list of sections, the section, and the item's detail page in them respectively.
Those. in index - catalog.section.list, in section - catalog.section and in detail respectively catalog.element.
Set up urlrewrite as needed and this is the best solution in my opinion. Of course, you can also use a complex component in one index file, but in my opinion this is a bad solution - it is less transparent, cumbersome and can lead to errors in working with urls, since it shifts control over the path settings on the site to you.

Answer 2

This is my first site

- Go through the training and then formulate your question again, but I think there will be no questions.
- I saw such nonsense at one online store, where instead of using the standard features of the system, and where you need to add and expand, it turned out to be a hard-to-support bike, where a step to the left, a step to the right, problems begin.
I do not recommend doing this, you will become a hostage to the wrong decisions.

Answer 3

the second, better for thematic quoting
, but Bitrix, I'm afraid, is not the solution that can be sharpened for a good Google Page Speed
, you try, look at traffic, SEO, you can always redo or combine