The problem
Why generic AI gets Barcelona wrong
Ask AI for a Barcelona itinerary and you'll get Sagrada Família, Park Güell, Las Ramblas, and Barceloneta Beach — all on day one. What the AI won't mention: Sagrada Família tickets sell out weeks in advance, Park Güell requires timed entry, and Las Ramblas is where pickpockets work, not where locals go.
Barcelona also lives on a completely different schedule to the rest of Europe. Lunch is at 2pm, dinner starts at 9pm and peaks at 11pm, and the nightlife doesn't begin until 1am. A generic AI prompt schedules dinner at 7pm and misses the entire point of the city. Eating early in Barcelona means eating alone, surrounded by other tourists.
🎟️
No booking logic. Sagrada Família, Casa Batlló, Casa Milà, and Park Güell all require advance tickets — sometimes weeks ahead in high season. AI never flags this until you've already planned your day around them.
🕐
Wrong meal times. Scheduling dinner at 7pm in Barcelona means eating in an empty restaurant serving a tourist menu. The real dining scene starts at 9pm. This changes your entire evening structure.
🗺️
Neighbourhood confusion. Eixample, El Born, Gràcia, Barceloneta, Poblenou — these are 20–40 minute walks apart. AI mixes them in the same half-day without transit context.
The fix
The structured Barcelona prompt — copy and paste
This prompt forces the AI to plan with real constraints — geography, transport, pace, and local specificity — instead of defaulting to a highlights reel.
Act as a Barcelona local who gives honest travel advice. Plan a 5-day Barcelona trip for a couple who want architecture, food, and nightlife.
HARD CONSTRAINTS — follow these exactly:
- Booking: Flag every attraction requiring advance tickets. Include how far ahead and the exact booking URL or method.
- Geography: Plan strictly by neighbourhood. Each half-day must be walkable within itself. Eixample, El Born, Gràcia, and Barceloneta are separate zones — never mix them.
- Meal times: Lunch 2–4pm. Dinner 9–11pm. No exceptions. Do not schedule any restaurant before these windows.
- Food: One specific named bar or restaurant per day — give the name, one dish to order, and whether booking is needed.
- Nightlife: At least one evening must start at a vermutería (name it) and end at a club or live music venue (name it). Include approximate timing.
- Avoid: Las Ramblas as a destination, any activity described as "vibrant" or "bustling" without specifics.
FORMAT:
Morning / Afternoon / Evening with neighbourhood label. Booking flags. One insider tip per day.
💡 Pro tip: Add one line at the end with your specific situation — group size, travel dates, any constraints. The more specific, the better the output.
Going further
Where this prompt still falls short
This template is a strong starting point, but a static prompt can't account for your specific trip. Here are three scenarios where you'll still get a mediocre result:
🌞
High season (Jul–Aug)
Every attraction is at maximum capacity. The prompt needs to add early-morning timing and alternative routes to avoid crowds at major sites.
🏈
FC Barcelona match
A Camp Nou match day changes the entire city — neighbourhood crowds, restaurant capacity, transport. If you want to attend, the itinerary needs to build around it.
🌧️
Off-season (Nov–Feb)
Beach and outdoor terrace logic disappears. The trip reorients around indoor markets, art museums, and a slower, cheaper, more local version of the city.
Zippy asks you the right questions first, then builds the prompt — and the full itinerary — around your exact situation.
Free · No sign-up · 60 seconds
Get your personalised Barcelona itinerary
Answer 6 quick questions. Zippy builds the neighbourhood-by-neighbourhood plan — real meal times, booking flags, local picks.
Build my Barcelona trip →