← Recent work

E-commerce / Cosmetics

e-fontanna.

A store I work on day to day.

Website e-fontanna.com.pl
e-fontanna.com.plRead the story ↓

Recording of the actual website.

Project story

The work continues after launch.

For e‑Fontanna, I work on the daily operation of a large store and the decisions behind its further development. I connect reporting with checks of SEO, links, delivery and the purchase journey, as well as preparation for the season. I implemented some changes; other work concluded with an audit and a concrete task list for the team.

The starting point

Keep a large store organised and identify changes that matter to both customers and the team running sales.

My role

I handle technical SEO, shopping-experience audits, reporting and planning further improvements. I develop the existing store.

883 URLs

A check of the public sitemap in the full audit of 4 October 2026.

15 prioritised tasks

The pre-season plan contains specific actions and criteria for checking them.

Comparable data

Reporting uses the same definitions of orders and value across several stores.

What I did

My work on the project

Reporting the store’s daily work

e‑Fontanna was included in the order-reporting mechanism under development. Daily and monthly summaries make it possible to check orders, their value and unit counts without manually combining several exports. Cancelled orders do not increase the result, and the data can be compared with the other stores using the same counting rules.

Indexing selected categories

I checked the role of category pages and their availability to customers and crawlers. Once the scope had been agreed, I introduced a conditional noindex rule for precisely specified routes. I also checked that other categories were unaffected. I treat an indexing decision as a deliberate change to a specific page, rather than automatically excluding an entire group.

Search Console links and the real store

I verified lists of historical errors and old URLs. I separated pages still returning 404 responses from working redirects and loops. I then checked the links customers can click today, because a historical Google report does not describe the whole current website.

A repair report, not just an error list

I prepared a spreadsheet with priority, incorrect target, source page and recommended action. One stage identified 16 broken content links and one loop in the menu. I separated technical URLs from the delivery module from the main shopping links. The audit produced a repair plan; the recommended redirects still require a separate implementation.

An independent assessment of the link profile

I compared Search Console data, material from previous audits and the actual linking pages. I checked both link targets and sources. The result did not provide grounds for mass link disavowal. Instead of an automatic operation, the outcome was a report, a spreadsheet and a recommendation to monitor specific sources.

Delivery, collection points and BaseLinker

I analysed DHL collection-point selection and the flow of order data into BaseLinker. I separated the collection-point map in the basket from label generation in store operations. I identified the integrations that required checking and the necessary test of collection-point data. This stage prepared the solution; full compatibility of the flow still requires confirmation.

Purchasing through the customer’s eyes

I went through the home page, categories, search, a product page, cart, discount, delivery options and order form, including on a phone. I checked whether payment and delivery information was consistent across pages. The test ended before placing and paying for an order, and I removed the test products from the cart.

Preparing for Black Friday

The full review covered promotions, prices, form consents, purchase information, the opening mobile view and 883 URLs from the sitemap. It produced a list of 15 prioritised tasks with criteria for checking them. A separate comparison of the purchase experience with Topestetic helped identify where a clearer product page or matching accessories could make the decision easier.

Stock planning begins with data but requires checks

I compared order periods and availability with the previous year's Black Friday. The plan distinguished demand, fulfilment status and the stock shown in the system. It identified products to discuss and a method for calculating opening campaign stock. Reservations, physical inventory and deliveries still have to be checked before approving a purchasing list. Commercial data remains outside the public portfolio.

Project timeline
  1. Shared reporting

    Development of e‑Fontanna order summaries alongside the other stores.

  2. Selected indexing rules

    Category checks and a controlled change for the agreed URLs.

  3. Links and redirects

    Audits of URLs and the link profile, with result spreadsheets prepared.

  4. Preparing the DHL integration

    Analysis of the pickup-point map and the data required by BaseLinker.

  5. Today's purchase journey

    Checks of content links, mobile shopping, delivery options and the cart.

  6. Full pre-season audit

    Promotions, consents, shopping, the sitemap and a comparison with Topestetic.

  7. Stocking plan

    Analysis of order periods and availability, plus a schedule of subsequent actions.

What comes next

The next stage is to implement the agreed priorities and check the purchase journey again after the changes. Any effect on conversion can only be assessed after implementation and measurement.

Next project

Artur Zawadzki