A website in Udine: the province the data calls former

A business site in Udine has to say on one screen what you do, where you are and how to reach you. The footer, which nobody watches while writing, is where wrong names pile up.

Udine has 97,808 residents in 2023, and the row we publish places it in "ex Provincia di Udine", Friuli-Venezia Giulia. The figure is read from Wikidata Q2790 on 1 November 2026 and describes the municipality, not a public body.

The pages a Udine business really uses

The footer holds three entries and gets them wrong often: the business name, the premises with its street number, and the tax details. Adding "Provincia di Udine" looks harmless, but the data we publish already calls it "ex", so it is not a name to present as an active body. The contact page deserves the same care.

"ex Provincia di Udine": what to write instead

In place of a body the data flags as former, write what exists: the business name, the address of the premises, the VAT number and the municipalities where you work. In structured data the LocalBusiness type takes addressLocality as Udine and addressRegion as Friuli-Venezia Giulia, while the working area goes into areaServed. The detail is in how to add schema markup.

A catchment is listed municipality by municipality

Working across several municipalities is an advantage: the list of names is clearer than any administrative label. "We serve Udine and nearby municipalities" says nothing; five names followed by a travel time say everything. If the business works in the city only, drop the list and write that: one true line beats three cautious ones.

# il footer nomina ancora la vecchia provincia?
curl -s https://www.esempio.it | sed 's/]*>/ /g' | grep -o -i "provincia di udine"

# regione dichiarata nei dati strutturati
curl -s https://www.esempio.it | grep -o '"addressRegion":"[^"]*"'

# la pagina dove siamo risponde
curl -s -o /dev/null -w "%{http_code}\n" https://www.esempio.it/dove-siamo

Three blocks from the catalogue

Footer 01 from Shadcn Space is the block with columns, contacts and a legal line: the right place for name, premises and VAT number. Contact 01 from the same publisher is the short form for phone and enquiries, with the fields that matter. The contact category holds the alternatives once the form needs more fields.

The limitation to state up front

The catalogue holds React and Tailwind components: there is no embedded map, no land registry or company register data and no integration with business registers. The blocks cover the interface; a verified address, the map and opening hours come from external services. On WordPress these blocks do not install as they are: they work as a structural reference.

Cost: the ranges are national

The 2026 ranges, published in what a website costs, are these: a landing page 400–1,200 euro, a five to ten page showcase site 1,500–4,000 euro, a structured company site 4,000–10,000 euro. Yearly maintenance for a small CMS site sits between 300 and 1,200 euro, the domain between 10 and 20 euro a year. They are national figures: there is no Udine price list, and a quote does not move with the name of the province.

For the minimum structure read what a company website needs, to appear in local searches get the site indexed by Google, to choose how to build it copy-paste or headless. Another city in the same group is a website in Trieste.