Technical SEO Consultant, Italy

When the catalog comes from the gestionale

In many Italian companies the website is downstream of the gestionale. Product codes, descriptions, variants, prices and availability are exported on a schedule, sometimes through a connector and sometimes through a spreadsheet someone uploads. Search engines see the result, and the result is only as clean as the export.

The points I trace from the source system to the published page:

• Identity. Whether one product has one URL, or whether each color, finish or packaging unit becomes its own page with near-identical text.
• Content fields. Which export fields fill the title, heading, description and markup, and how many products arrive with those fields empty or copied from a supplier.
• Life cycle. What happens to items that are out of stock, replaced or withdrawn: a page with alternatives, a redirect to the successor, or an empty page that still returns a normal status.
• Resync side effects. Whether the nightly import recreates pages that were deliberately removed or overwrites edits made on the website.

Fixes often belong in the export logic rather than the CMS, which is why I write them so both the web agency and whoever maintains the gestionale integration can act. When the integration itself needs redesign, that is a systems question covered by my ERP integration work and my ERP consulting in Italy. The audit method is the one on my technical SEO audit page.

Filters, variants and seasonal collections

Italian shops selling fashion, furniture, food and wine, cosmetics or components share one technical risk: filters. Every combination of size, color, material, region of origin, price band and sort order can produce a new URL. Left alone, crawlers spend their time on thousands of filter pages while new products wait to be discovered.

The answer is not to block everything. Some filter pages match real searches, such as a category by material or a wine list by region, and deserve to be proper landing pages with their own title, text and stable URL. Most combinations do not. I classify them with you:

• Indexable filter pages, chosen from keyword research and linked from navigation.
• Crawlable but non-indexable combinations, for convenience without index bloat.
• Parameters for sorting, view mode and tracking, kept out of crawling altogether.

Seasonal collections add a second layer. Fashion and design brands replace collections regularly, and old collection pages often vanish with no redirect, losing the links they gathered. A simple rule set covers this: permanent category pages that persist across seasons, collection pages that redirect to their successor or the category when retired, and product pages kept live with alternatives while they still earn traffic.

The ecommerce SEO page covers the commercial side of these decisions; the technical side lands in your agency's backlog as clear tickets.

Accents, apostrophes and Italian URLs

Italian slugs raise two character questions. The first is accented vowels: à, è, é, ì, ò and ù. They can stay in the URL, where browsers show them normally and servers send them percent-encoded, or they can be reduced to plain vowels. The second is elision. Phrases such as dell'olio, l'azienda or un'offerta contain an apostrophe that slug generators handle in different ways: dropping it, turning it into a hyphen or encoding it.

None of these choices is wrong in itself. Problems start when a site uses several at once, which is common after years of plugins and agency changes:

• Old pages with dellolio, newer ones with dell-olio, and a redirect rule that only knows one form.
• Hreflang references written with a different encoding from the canonical, so the pair never matches.
• Capital accented letters such as È handled differently from lowercase ones.
• Reports splitting one page across several URLs, hiding its real performance.

I document one rule for accents, elisions and capitals, ask the developers to enforce it in the slug generator, and check that legacy forms redirect to the chosen one. Existing URLs only change when the benefit outweighs the redirect risk.

Fonts belong here too. A web font subset that leaves out accented glyphs makes the browser substitute a fallback for single letters, which looks untidy and can shift the layout during loading.

PDF catalogs, dealer portals and what search engines can see

Italian B2B companies often publish their real expertise as downloadable catalogs: dimensions, tolerances, materials, finishes and compliance information inside large PDFs. Search engines can index PDFs, but a buyer landing deep inside a catalog has no navigation, no contact path and no context. The product page, meanwhile, says little.

The technical fix is to move the searchable facts into HTML: specification tables on product pages, application pages for each use case and a downloads area that links each PDF from the page it belongs to. The PDFs stay available, but they stop competing with the pages you want people to land on.

Two further areas need a decision:

• Dealer and reserved areas. Price lists, technical drawings and documentation behind a login cannot be crawled. Decide which content should be public, because anything behind the login does not exist for search.
• Configurators and JavaScript components. Product configurators and dynamic catalogs may render content only in the browser. A side-by-side of the HTML the server sends and the page after scripts run confirms that names, specifications and links are visible to crawlers, using the method on my JavaScript SEO page.

Once the facts sit on HTML pages, product and organization markup can describe them accurately, as outlined under schema markup consulting, and the pages become useful sources for AI-generated answers as well.

Speed, consent tools and working with your agency

Italian sites tend to be visual, and visual sites are heavy. Large hero images, sliders, video backgrounds, chat widgets, review badges and several marketing tags all compete for the first moments of loading on a phone. Connections also vary between cities, smaller towns and mountain areas, so pages that feel fast in the office can struggle elsewhere.

I use field data from Search Console and real-user measurements to find the templates with problems, then lab tests to isolate causes. Consent tools deserve their own check: depending on configuration, the banner, the consent platform and the tags waiting behind it can delay content and interaction. GDPR and the Italian data protection authority's guidance shape the consent design, which is your legal advisor's call; I make sure the technical implementation is efficient. The Core Web Vitals consulting page explains the approach.

Most Italian sites are maintained by an external agency, and the work is designed around that relationship. Each finding becomes a ticket describing what happens now, what should happen and how to test it; a review call settles priorities, and I verify fixes on staging and in production. When the agency proposes a new platform or redesign, the redirect map and launch checks follow SEO migration consulting.

Everything is delivered remotely. For export markets see my international SEO page for Italy; for the wider search plan, my SEO consulting in Italy; and the Italy hub for the other services.