Standard: “paired product names → created tags → growing”. The reception works well, but what does this process look like in Print Bar? Naming of cards plays an important role for the growth of traffic on the website of prints. They already have some name, but there is often a problem of duplicates. For example, there may be 40 cards with the same name on 1 listing, which breeds non-uniqueness and other problems. Printbar solves such tasks using SEO admin renaming and subsequently monitors traffic dynamics in DATAFORCE.
It is also important for the context, SMM, and email departments to monitor what sells well, where traffic goes, and where it disappeared, what is converted better, and so on. A quick reaction to changes will not allow the business to lose profit.
Google Data Studio found old product cards that stretch from a very old site structure, but at the same time brought good traffic to Google. However, at that time it was not possible to understand exactly how much, because it was not possible to build a mask. The team decided to make 301 redirects. Some of them moved to a new structure, but mostly lost about 4.5 thousand traffic.
Enabled the uml API
At the start there were about 1400 feeds, which is equal to 53 million offers. There were really a lot of offers, but you can tag them using utm — convenient for internal analytics. There was a good increase in traffic
Over time, we decided to reduce the number of feeds and now there are about 250 = ~ 6.6 million offers — traffic is gradually starting to grow
The percentage of visitors who made an order = ~3%
The addition from Yandex is interesting, there are its own features. For example, if Printbar does not have a card or a listing in the index, but at the same time a person makes a request with a print and gets into the right name, then your project will appear. This allows you to always get some share of traffic.