WordPress developer in Milan

WordPress development for Milan companies by one remote developer in Poland, in English. Italian texts come from you. Garante cookie rules and the website identity duties of D.Lgs. 70/2003 built into the scope.

WordPress developer

My place in the WordPress community

  • I have had a wordpress.org account since 2006.
  • I contributed to WordPress core for versions 7.0 and 7.1.
  • I maintain 30 plugins on wordpress.org.
  • I organise and speak at WordCamps.
  • I have attended every WordCamp Europe from 2017 to 2026.
  • Local WordPress meetup: WordPress Meetup Milano

My WordPress.org profile

I am Mariusz Szatkowski, a WordPress developer in Gdynia, Poland, and I have worked with WordPress since 2006. If you searched for “sviluppo WordPress Milano” or for an Italian WordPress developer, one thing first: I am not Italian and I do not write Italian. I work for Milan companies remotely, in English, and the Italian texts on the site come from you. What I bring is the code, the structure and a build process that keeps Italian legal requirements in the acceptance list instead of leaving them for after launch.

#Who this page is for

This page fits a Milan company that already writes its own content, or has someone who does, and needs a developer to turn a layout and a set of requirements into a working WordPress site. Typical starting points:

  • a company site in Italian and English that has outgrown a page builder and needs clean templates and structured content;
  • a site built years ago by an agency that is no longer around, with plugins nobody dares to update;
  • an export business that wants product or service pages in several languages, each with its own URL and search visibility;
  • an editorial team that wants Gutenberg blocks and custom fields so pages can be built without calling a developer.

Graphic design, mockups and wireframes are not something I produce. You bring the layout, either from your designer or by filling in a spreadsheet where you mark which elements go where on each view. I implement that as a responsive WordPress theme.

#Milan companies and multilingual sites

Piazza Gae Aulenti, Milan

Photo: DaveM93, CC BY-SA 3.0, Wikimedia Commons.

On 11 June 2026, for the DigIT Export Day, Assolombarda published results of a Promos Italia survey on how companies in the provinces of Milan, Monza Brianza and Lodi use digital tools for export. The event had the support of the Camera di commercio Milano Monza Brianza Lodi and its Punto Impresa Digitale. The sample was small, 47 companies that export or plan to, surveyed in May 2026, so I read the figures as a signal rather than a census:

  • 68 percent use their own digital channels, such as the website and e-commerce, as the main tool for developing business abroad;
  • 84 percent have a website in languages other than Italian;
  • 16 percent say their site is updated regularly but not yet adequately optimised.

The last figure is the one that matters for a developer. A site that exists in three languages but loads slowly, has broken hreflang or ships the English menu on the German pages loses the visitors that the translation was meant to win. The fix is rarely a new design. It is usually structure: one content model, clear language URLs, translated slugs, menus and forms per language, and an editor workflow that shows which pages are missing a translation.

This is also where working in English with a Polish developer is less strange than it sounds. When a Milan company writes to buyers in Germany, Spain or the UK, the English version is often the reference text that the other languages are checked against. I work from that version, and you or your translators supply each other language.

#What I build in WordPress

  • Custom themes from your layout. Block themes or classic themes, depending on what your editors need and what the existing site uses. Templates follow the layout you provide, with accessible markup and no page builder lock-in.
  • Gutenberg blocks and patterns. Blocks for the sections your editors repeat (product highlights, team lists, downloads, contact boxes), so pages are built from pieces you control.
  • Custom post types and fields. Products, projects, events, locations or vacancies stored as structured content, not as long pages with copied layouts.
  • Plugins for your own logic. Integrations, forms with server-side validation, REST endpoints for a CRM or an ERP. Anything that must survive a theme change lives in a plugin.
  • Multilingual setup. Separate URLs per language, hreflang, translated slugs and menus, and language-aware forms.
  • WooCommerce where you sell online. For shop-specific work see the WooCommerce developer page for Milan.

Performance targets are the official Core Web Vitals thresholds, LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1, as defined on web.dev. I check them on the templates you name, before release.

#Cookies: what the Garante guidelines ask of the build

The Italian legal basis for cookies is article 122 of the Codice in materia di protezione dei dati personali (D.Lgs. 196/2003), which allows storing or reading information on a user’s device only with consent, except for technical purposes. How that works on a real site is set out in the Garante guidelines on cookies and other tracking tools, adopted on 10 June 2021 and published in the Gazzetta Ufficiale no. 163 of 9 July 2021. Several of its points translate directly into code:

  • The X button. Closing the banner with the X keeps the default settings, so the visitor continues without non-technical cookies. The banner must say so, and the close button must not quietly mean “accept”.
  • Scrolling. The guidelines state that scrolling alone is never suitable as consent. A script that treats a scroll as agreement fails the test.
  • Cookie walls. Blocking access until the visitor accepts is considered unlawful, unless the site offers an equivalent way in without consent; the Garante says this must be assessed case by case.
  • Not asking again too soon. The banner should not be shown again until at least 6 months have passed since it was last shown, unless something material changes, such as new third parties, or the earlier choice cannot be read back.
  • What the banner contains. A short notice that closing with the X keeps the defaults, minimal information on technical and profiling cookies, a link to the full policy (also reachable from the footer), a button to accept all, and a link to a granular area where every option starts switched off.
  • Analytics. Analytics cookies may count as technical only under conditions, among them masking at least the fourth component of an IPv4 address, use for aggregate statistics on one site or app, and no combining or passing on of the data by the third party.

In practice, the work on my side is: a consent tool configured to block marketing and analytics scripts until the visitor agrees, embeds (maps, videos, fonts from third-party hosts) held back or replaced by a click-to-load placeholder, a consent record that survives the 6-month rule, and a staging test where I check in the browser which requests fire before and after the click. The wording of the banner and the cookie policy comes from you or your adviser. I do not give legal advice; I make the site behave as your policy says.

#The company data your site must show

Italian law also asks a website to say who runs it. Article 7 of D.Lgs. 70/2003, which implements the EU e-commerce directive 2000/31/EC, lists the general information a provider of information society services must make available:

  • name, company name or business name;
  • domicile or registered office;
  • details for contacting the provider quickly, including an email address;
  • the REA number or the company register number;
  • for activities under a concession, licence or authorisation, the details of the competent supervisory authority;
  • for regulated professions, the professional body and registration number, the professional title and the member state that granted it, and the applicable professional rules;
  • the partita IVA, or an equivalent identification number, where the activity is subject to tax.

On many older sites this information sits on one “Chi siamo” page, or in a footer that one template forgot. I put it in a single place in the WordPress settings, render it in the footer of every template and every language version, and add it to the acceptance list so a later theme change cannot drop it.

#From brief to release: the steps of a Milan project

  1. Your brief. The site address if there is one, the goal, the deadline, the layout and what you know about hosting and plugins.
  2. My questions, in writing. Usually about content ownership, languages, integrations and who approves what.
  3. Written scope and assumptions. What is in, what is out, what I assume. This is where Italian texts, translations, legal texts and photos are assigned to you, so nothing is waiting on a misunderstanding.
  4. Build on staging. You get a staging address and can follow the work. Changes go in small steps with notes.
  5. Acceptance. You test against the agreed list: templates, forms, languages, cookie behaviour, company data, Core Web Vitals on the named pages.
  6. Release and handover. Go-live as a documented step with a backup and a way back. You get notes for editors and for whoever maintains the site next.

If you want someone to keep the site updated after launch, the WordPress maintenance page for Milan describes that part.

#What you prepare

  • The layout: from your designer, or my spreadsheet template with the elements per view.
  • Texts in every language you publish, reviewed by someone who writes that language.
  • The privacy policy, the cookie policy and the banner wording, from you or your adviser.
  • The company data for article 7 of D.Lgs. 70/2003.
  • Access to the current WordPress, the hosting panel and the domain, if a site exists.
  • A list of the pages and forms that must never break.

#A checklist for any Milan WordPress site

You can run this against your current site whether or not you hire me.

QuestionWhat a good answer looks like
Does closing the banner with the X load any tracker?No, checked in the browser network panel
Does scrolling count as consent?No
Are all choices in the granular area off by default?Yes
Is the analytics IP masked, or does analytics wait for consent?One of the two, documented
Are REA number, partita IVA, registered office and email in the footer?Yes, on every language version
Does each language have its own URL and hreflang?Yes, and the alternates point at each other
Who can edit the Italian and English texts without a developer?A named person
Is there a staging copy for testing changes?Yes

#Questions Milan companies ask

#Do you speak Italian, and who writes the Italian texts?

No. I am Polish and I work in English. The Italian copy, the privacy policy and the cookie policy come from you, your team or your translator or lawyer. I build the site so those texts can be entered, reviewed and updated by your editors.

#Do you come to Milan for meetings?

No. I work remotely from Gdynia in Poland and everything runs in writing: brief, questions, scope, staging links and acceptance. Access to the site, the hosting and the layout is what I need.

Under the guidelines of 10 June 2021, closing the banner with the X keeps the default settings, scrolling is never consent on its own, a cookie wall is unlawful unless an equivalent alternative exists, and the banner should not come back for at least 6 months unless something material changes. I implement that behaviour and check it on staging.

#Which company data must appear on the website?

Article 7 of D.Lgs. 70/2003 lists them: name or company name, registered office, contact details including email, REA or company register number, partita IVA where the activity is taxable, and more for regulated professions or licensed activities. You supply the data, I place it where it is easy to find on every page.

#Can my site run in Italian and English, or more languages?

Yes. I set up a multilingual structure with separate URLs, hreflang and menus per language. Each language version needs its own reviewed text from you, not machine output pasted in.

#Can you take over a WordPress site another agency built?

Yes. I start with an inventory of the theme, plugins, PHP version, hosting and backups, then send a written list of what to fix before new work begins.

#Write to me

Send me your site address if you have one, what the site should do for your business, your deadline, and what you know about the current stack and hosting. If you already have a layout or a list of languages, attach it. I read everything, reply with my questions in writing and then send a written estimate with scope and assumptions. The first estimate is free. The contact page has the form, and an overview of the service is on the WordPress developer page.

See also in Italy

Need this service: WordPress developer in Milan?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Latest WordPress developer articles

Sep 14, 2017

WordPress history, from 4.9 to the Gutenberg era

WordPress 4.9 was "the calm before the storm." We analyze this pivotal moment in WP history that prepared the ground for the block editor. What changed since? How did the ecosystem evolve?