Elope in Italy

The direction, applied

Already Designed is now described by its venue, not by its add-ons. The private dinner and the activity still come with it, but they are no longer what makes a package qualify — the secured venue is. The filter row leads with venue type for the same reason.

Nothing moves

Every designed experience keeps the slug it already has in the repo — /tuscany-chapel-luxury-elopement-package and the rest — and the _redirects file already carries the 301s from the old premium-elopement-package-no-N URLs. The structured data on this page has been corrected to the real slugs; it was still pointing at the numbered ones.

Both doors now have a price

The open flag from the first prototype is closed. Every destination page already carries a classic "from" price — €5,000 in Langhe and Matera up to €9,000 on Como and Garda — so it is now on every destination card here. The two doors read as equals because both of them have a number.

Venues are named — decided 24 September

The SEO case rests on naming the venue: "casa angelina elopement" is only reachable if the page says Casa Angelina. The team decided to name them. Eight venues come from the private quote pages and now lead each experience's page title, its card and its venue section.

Still to name: the Lake Garda villa and the Apulian masseria, which have no quote page yet.

The example page

Villa del Balbianello is in the grid with no price, marked as an example. It exists to show what the new shape looks like when the venue is named and the package is named after it — and to make the question above concrete before we commit to five of them.

One package has no page

The grid lists a Lake Garda villa experience at €15,800. There is no package page for it in the repo and no lake-garda-villa-luxury-elopement-package slug — only nine of the ten exist. Its page here is written to the house pattern so the link works, but the copy and the price both need confirming.

A copy bug on the live page

On the current /elopement-italy, the Lake Garda paragraph opens "Lake Como elopements let you celebrate on the shimmering waters of northern Italy…" — the wrong destination name, live today. It is corrected on the Lake Garda page here. Worth fixing on the live page whatever happens to this redesign.

The long copy is kept

The warning from the first prototype still stands, so it has been acted on: the full paragraph that each destination carries on the live Italy page now lives on that destination's own page, under its own H2, alongside the page's existing intro. The cards carry one line; the words that rank are still on the site, just one level down.

Three ways to show them — pick one

Use the switch in the black bar at the top of the page. Nothing here is decided.

• One grid. What the page has today. Honest and simple, and fine up to about twenty. Past that the filters are doing all the work and the page is just long.
• Grouped by place. One short row per destination, a swipe on a phone. Scales indefinitely because Tuscany will never hold ninety venues — but it reads like a catalogue, which is a lot of thumbnails for a €17,000 decision.
• Six, by landscape. The Italy page shows six, chosen, with a line each on why — grouped as coast, lakes, countryside, which is how a couple picks before they pick a region. Everything else moves to one filterable page. This is the one I would ship.

The third is the only one where adding Italy’s ninetieth experience changes nothing about this page. It also puts the filtering where it belongs: you already have /elopement-experiences and /luxury-elopement-packages doing roughly this job.

The one that would make us different

None of the three is a differentiator — they are layouts. The thing no competitor does is filter by when. “When are you thinking?” is the most qualifying question on your calls and it cuts a catalogue harder than budget or region does: half these venues are wrong in November.

It needs a season on every venue record, which is real work for Cyntia, Lara and Florencia. Worth it once the catalogue is big enough to need cutting.

Still true for the real build

• Ship all 25 cards in the HTML and let the filters only hide them. Filtering is a CSS problem, not a rendering one — what you see here is drawn by JavaScript, which is fine for a mockup and risky for Google.
• Each package and destination is a record with fields — area, price, landscape, venue type, activities — not a hand-written page. Every filter reads those fields.
• One source of truth for price, so a card and its page can never disagree.
• If filters ever write to the URL, canonical them back to /elopement-italy.

Your open question

The packaging note asks whether "already designed" goes on the site now or stays internal until the tier is proven. This mockup assumes yes, now — the words appear as a section heading, a badge on each package page and a filter label, and nowhere else. If you would rather hold, the change is three strings; the structure does not depend on the name.

"Classic" stays gone from the page either way. The destination door describes itself without it.