Magento ver. 2.4.6
Filters will be implemented by the module “Amasty Improved Layered Navigation” using the functionality “Improved Layered Navigation: Pages - Custom Pages”
An estimate is needed for the implementation of the task.
And your vision for the implementation.
Regional subfolders need to be implemented, which will make the website pages more relevant to search queries.
Technical assignment for development
Recommendations for implementing regional versions of the website:
1. The URL is formed by adding the subfolder /[city name]/.
Example:
https://www.site.ua/odessa/
https://www.site.ua/ua/odessa/
Example:
https://www.site.ua/odessa/vitaminy/
https://www.site.ua/ua/odessa/vitaminy/
- Subcategory (Vitamins for Men)
Example:
https://www.site.ua/odessa/vitaminy/vitaminy-dlja-muzhchin/
https://www.site.ua/ua/odessa/vitaminy/vitaminy-dlja-muzhchin/
- Information page (remains unchanged in the regional version)
- Product (remains unchanged in the regional version)
2. Only the URLs of sections, categories, filters, and the main page should change in the regional versions, as these pages will be unique. All other pages will be without the city prefix to avoid content duplication.
Example of implementation:
3. Uniqueness. It is necessary to make all metadata and H1 headers unique by using the prefix “in [city name]”. For primary uniqueness, use templates.
Also, regional versions of pages should not contain text descriptions of the main pages; they should either be without text or contain unique text.
4. It is necessary to implement the determination of the user's IP address, based on which the site will be assigned a specific region. (NOT DOING THIS YET)
5. The main version of the site (without a subfolder, e.g.: https://www.site.ua/) should be linked to the Kyiv region.
6. In the website database, for each city, it is necessary to specify the name of the city in the prepositional case + the preposition “in”, for example: Odessa — in Odessa.
7. It is necessary to create a rule according to which for any page of the site, if a city from those available in the database is selected, the metadata, headers, and breadcrumbs (except for the main page) should be constructed according to the following rule:
H1 Header
{Default H1 Header} + {value from the city names table in the prepositional case with the preposition “in”}
Example for https://www.site.ua/odessa/sportivnoe-pitanie/-> H1: “Sports Nutrition in Odessa”
Title:
{Default H1 Header} + {value from the city names table in the prepositional case with the preposition “in”} buy at a low price | MedTech
Example:
Sports Nutrition in Odessa buy at a low price | MedTech
Description:
{Default H1 Header} + {value from the city names table in the prepositional case with the preposition “in”} buy at a price from {minimum price value for available products in the category for which the tag is built} UAH! ➤ Online store ✚ MedTech ➤ Wide selection ✔️ Quality guarantee ✅ Low prices ⚡ Promotions ⚡
Example:
Sports Nutrition in Odessa buy at a price from 18 UAH! ➤ Online store ✚ MedTech ➤ Wide selection ✔️ Quality guarantee ✅ Low prices ⚡ Promotions ⚡
8. The website database MUST HAVE THE POSSIBILITY for each page formed as a result of selecting a city from the list, as well as the nested structure, to apply META-data according to the template and manually, as well as to place unique textual content on any of the resulting pages.
9. Metadata with partially manual values, proposed earlier can be filled in after applying the main template (for regional pages, manual filling is not critical - due to the scale, manual data can be implemented gradually).
10. The database must reserve fields for the values of the H1 header of this page, the <title> tag, <meta name=”description” content=”” />, the Canonical tag, and the robots meta tag.
11. Visually, the city selection should preferably be located in the website header - where there will be a list of cities for which static content is provided for regionality. If there are no static pages - then the city name should not be displayed in the list.
12. Hreflang alternate tags on regional pages should work the same way as on pages without a region - the current version with its language and the alternative version - regional with an alternative language.
13. The admin panel of the site should provide the ability to set the value of flexible indexing of filters for this region.
Example:
- For region N, we set that filter combinations of 2 levels are indexed: category + 2 filters
- For region M, we set that 1 level combinations are indexed: category + 1 filter
- For region Y, we set that filters are not indexed (value 0)
!!! By default, at the start stage, for all regional pages, the combination category + 1 indexed filter is open for indexing.
