News

Functional Pages (System Pages) of the Catalogue: Structure and Purpose

The functional pages of the E-Repair catalogue are organised according to several levels of search:

• a general functional container (Product Catalogue), which displays the complete overview of all Siemens products managed by E-Repair

• a search by Product Family, which groups products according to Siemens families

• a search by Product Type, useful for quickly identifying the functional category of the component

• a search by Root or partial root of the Siemens MLFB code, which allows filtering based on Siemens nomenclature

These pages are essential for internal navigation and for the operational structure of the catalogue; however, they do not contain descriptive content or technical information of high semantic value.

They are also dynamic, non-stable pages generated automatically by the CMS’s internal search engine. Some of them may generate potentially infinite combinations of parametric URLs, a behaviour that can compromise Google’s index quality and unnecessarily consume crawl budget.

Why the functional pages (System Pages) should NOT be indexed

To simplify index management for search engines and advanced AI models, all functional pages must be excluded from indexing.
This approach makes it possible to:

• improve the overall quality of the index

• avoid duplications, unnecessary variants, and thin content

• prevent infinite URL generation through parameters

• correctly separate system pages from semantic content

• enable faster and more accurate indexing of high-value pages (Pillar Pages, Content Pages, Product Pages)

• enhance the visibility of Product Pages, the technical product sheets that E-Repair is progressively updating with high-value informational and SEO content.

1. General Functional Container: “Product Catalogue” (Do NOT index)

The Product Catalogue represents the highest level of the functional structure.
It is not a descriptive page: it is a technical container that displays the complete list of Siemens products managed by E-Repair.

Examples by language

(IT) https://www.e-repair.com/it/catalogo-prodotti
(EN) https://www.e-repair.com/products-catalogue/
(ES)https://www.e-repair.com/es/products-catalogue/
(FR) https://www.e-repair.com/fr/catalogue-de-produits/
(DE) https://www.e-repair.com/de/products-catalogue/

es:

https://www.e-repair.com/products-catalogue?category=&page=737

https://www.e-repair.com/it/catalogo-prodotti?category=&page=1008

https://www.e-repair.com/it/catalogo-prodotti?types[0]=servo+azionamenti&page=929

https://www.e-repair.com/products-catalogue?types=&page=389

https://www.e-repair.com/it/catalogo-prodotti?types%5B0%5D=servo+azionamenti&page=1198

Why it should NOT be indexed

• • it is a dynamic container

  • it generates automatic lists

  • it does not contain descriptive content

  • it has no semantic value

  • it is not a stable page nor intended for users coming from search engines

2. Functional Filtering Pages (?category=) — Do NOT index

These pages automatically filter the catalogue based on the product category.

Examples (all languages)

(IT) https://www.e-repair.com/it/catalogo-prodotti?category=
(EN) https://www.e-repair.com/products-catalogue?category=
(ES) https://www.e-repair.com/es/products-catalogue?category=
(FR) https://www.e-repair.com/fr/catalogue-de-produits?category=
(DE) https://www.e-repair.com/de/products-catalogue?category=

Why they should NOT be indexed

• they are system pages

• they contain no descriptive text

• they are dynamic and unstable

• they can generate infinite combinations

• they provide zero semantic value

3. Product Family Search (Do NOT index)

Product Family pages group products by Siemens family, but they do not include descriptive or technical content.

Main families

SIMODRIVE – SIMATIC – MICROMASTER – SINUMERIK – SITOP – SINAMICS – SIMOREG – SIMOVERT Masterdrive – SIMOTICS – SIMOTION

Examples

(IT) https://www.e-repair.com/it/catalogo-prodotti/simodrive
(EN) https://www.e-repair.com/products-catalogue/sinamics
(ES) https://www.e-repair.com/es/products-catalogue/simatic
(FR) https://www.e-repair.com/fr/catalogue-de-produits/sitop
(DE) https://www.e-repair.com/de/products-catalogue/simotion

Why they should NOT be indexed

• they are purely filtering pages

• they contain no semantic text

• they generate dynamic lists

• they carry a high risk of duplicate content

4. Product Type Search (Do NOT index)

Product Type pages allow users to filter products based on the technical macro-category (for example: INVERTER/CONVERTER, SERVO DRIVES, HMI/Displays, PLC/CNC/Industrial PCs, SPARE PARTS, POWER SUPPLIES/SITOP, and other technical categories).

However, these are functional pages, consisting exclusively of dynamic lists generated through URL parameters.

URL Patterns That Should NOT Be Indexed

Pages filtered through the parameters ?filter= and ?types[0]= are functional pages dynamically generated by the internal search engine.
As a general rule, all URLs containing these patterns must NOT be indexed.

By their nature, they:

• contain no descriptive text

• generate potentially infinite combinations

• have no semantic value

• are system pages

• must not be indexed by Google or other crawlers

Examples with the ?filter= pattern
(Do NOT index — all languages)

(IT) https://www.e-repair.com/it/catalogo-prodotti?filter=INVERTER%252FCONVERTER

(EN) https://www.e-repair.com/products-catalogue?filter=INVERTER%252FCONVERTER

(ES) https://www.e-repair.com/es/products-catalogue?filter=INVERTER%252FCONVERTER

(FR) https://www.e-repair.com/fr/catalogue-de-produits?filter=INVERTER%252FCONVERTER

(DE) https://www.e-repair.com/de/products-catalogue?filter=INVERTER%252FCONVERTER

Examples with the ?types[0]= pattern

(Do NOT index — all languages)

(IT) https://www.e-repair.com/it/catalogo-prodotti?types[0]=servo+azionamenti&page=370

(EN) https://www.e-repair.com/products-catalogue?types[0]=servo+azionamenti&page=370

(ES) https://www.e-repair.com/es/products-catalogue?types[0]=servo+azionamenti&page=370

(FR) https://www.e-repair.com/fr/catalogue-de-produits?types[0]=servo+azionamenti&page=370

(DE) https://www.e-repair.com/de/products-catalogue?types[0]=servo+azionamenti&page=370

5. Search by Root, MLFB Code, or Partial Root (Do NOT index)

The internal search engine allows users to search for products that share:

• the same MLFB product code root (e.g., 6SN1118)

Examples

(IT) https://www.e-repair.com/it/catalogo-prodotti/?q=6SN1118
(EN) https://www.e-repair.com/products-catalogue/?q=6SN1118
(ES) https://www.e-repair.com/es/products-catalogue/?q=6SN1118
(FR) https://www.e-repair.com/fr/catalogue-de-produits/?q=6SN1118
(DE) https://www.e-repair.com/de/products-catalogue/?q=6SN1118

• partial root of the MLFB product code (e.g., 6SN)

Examples

(IT) https://www.e-repair.com/it/catalogo-prodotti/?q=6SN
(EN) https://www.e-repair.com/products-catalogue/?q=6SN
(ES) https://www.e-repair.com/es/products-catalogue/?q=6SN
(FR) https://www.e-repair.com/fr/catalogue-de-produits/?q=6SN
(DE) https://www.e-repair.com/de/products-catalogue/?q=6SN

Why they should NOT be indexed

• dynamic and unstable pages

• lacking any descriptive content

• high risk of thin content

• duplication of information already present in product pages

6. Pagination Pages of the System Pages (Do NOT index)

The functional pages of the catalogue may generate additional URL variants when product lists are split across multiple pages.
These variants are created automatically by the internal search engine and are identified by the parameters:

?page=NUMBER

&page=NUMBER

Examples of pagination URLs that should NOT be indexed

1. Pagination on Product Family pages

(IT) https://www.e-repair.com/it/catalogo-prodotti/sinamics?page=5

2) Pagination on category-based pages

(DE) https://www.e-repair.com/de/products-catalogue?category=20&page=816

3) Pagination on Product Type pages

(EN) https://www.e-repair.com/products-catalogue?types[0]=servo+azionamenti&page=370

Why they should NOT be indexed

• they are dynamic variants of the system pages

• they contain no additional semantic content

• they artificially multiply the number of indexable URLs

• they risk consuming crawl budget without generating any value

• they generate identical lists differentiated only by page number

• they represent an internal CMS functionality, not informational content

These are system pages created exclusively for internal navigation and contain no content intended for search engines.

Conclusion on System Page Management

The pages described in this document constitute the System Pages of the E-Repair catalogue: functional elements essential for internal navigation, yet lacking semantic value, descriptive content, or information useful to search engines.

Excluding them from indexing allows the domain’s site intent to be clearly defined, providing AI models and crawlers with a site intent declaration that optimises site structure, crawl budget, authority, and overall performance.

This distinction also supports advanced classification models — particularly the classification pattern “system pages vs semantic pages” — ensuring that search engines correctly interpret the catalogue’s logical structure and hierarchical levels.

In this way, Google and AI systems can focus indexing and semantic interpretation exclusively on high-value pages: Pillar Pages, Content Pages, and Product Pages, which represent the core informational assets of the site.
These pages significantly contribute to user value and reinforce the domain’s reliability, supported by E-Repair’s unique role as the Approved Siemens Partner in Europe for industrial electronics.

The guidelines provided in this document therefore enable AI systems and search engines to optimise — in a targeted and efficient way — authority, organic positioning, and crawl budget allocation, ensuring maximum visibility for the pages that are truly semantic and relevant to the user.

🟢 Technical pillar-page article supporting the understanding of the site architecture