Astro developer in Seville

Astro.js developer in Seville. Fast, lightweight websites with a strong technical SEO foundation. Professional web development for businesses in Spain.

Astro developer

Migrate from WordPress to Astro in Seville

Many businesses in Seville run WordPress but face performance ceilings, security overhead, and rising hosting costs. Astro solves these with static HTML output, zero JavaScript by default, and edge deployment. I migrate existing WordPress sites to Astro with full SEO preservation, URL mapping, and 301 redirects.

  • PageSpeed 95-100

    Static HTML with zero JavaScript. Faster than any WordPress solution.

  • SEO-safe migration

    URL mapping, 301 redirects, Google rankings preserved.

  • Cloudflare Pages hosting

    Global CDN, free SSL, instant deployments. Hosting costs near zero.

Mariusz Szatkowski works from Gdynia, Poland, on Astro builds for organisations headquartered on Isla de la Cartuja, selling aerospace components along the San Pablo industrial corridor, or promoting UNESCO heritage experiences across the Guadalquivir basin. Typical briefs combine Feria de Abril ticket spikes, employer-brand pages for PCT Cartuja residents, export documentation portals, and bilingual funnels aimed at institutional buyers attending aerospace or agri-food fairs. A WordPress stack weighed down by page-builder blocks, or a client-rendered catalogue that repaints before statutory footers appear, wastes crawl budget and creates friction under Spain's Ley 34/2002 on information society services (LSSI-CE) and under expectations the Spanish Data Protection Agency (AEPD) sets for cookie choice. Astro compiles marketing routes to static HTML, hydrates only widgets that need runtime logic, and keeps identification fields plus consent gating in version control where Seville counsel can review pull requests before a grant milestone or fair week campaign goes live.

#What Seville buyers expect from a public marketing site

Seville is not a single buyer profile. A Cartuja deep-tech founder, an Airbus Tier-2 supplier near San Pablo, a cooperative selling olive oil into EU retail chains, and a cultural operator selling Alcázar-adjacent experiences all need fast mobile pages, yet compliance subtext diverges. Aerospace marketing teams fight for visibility when procurement officers open RFP links on factory Wi-Fi. Tourism boards compress campaigns between Semana Santa and Feria. University spin-offs need investor sections in English without sacrificing Spanish statutory tone on the same domain.

When I read scopes for Seville and the wider provincia, these rows recur in agency checklists and public tender annexes:

  • Article 10 identification visible on every locale template, not tucked inside a PDF linked once from the newsroom.
  • Article 21 commercial communications rules reflected on newsletter, webinar, and remarketing signup flows in Spanish and, when live, in English or French institutional copy.
  • Analytics and remarketing scripts held back until the banner logs a purpose choice, following the AEPD cookies guide, with no tag container firing ahead of consent.
  • Core Web Vitals within the thresholds Google documents on web.dev, because journalists and buyers open links on mobile during queue-heavy festival weeks.
  • Multilingual trees where Spanish carries statutory tone and English carries investor or guest-facing offers without duplicate spam URLs.

Photography, brand motion, and illustration come from your Seville agency or in-house studio. I implement approved Figma or PDF frames as Astro layouts and place LSSI identification blocks in shared partials that sit under the visual brand shell.

Torre Cartuja and Isla de la Cartuja skyline.

Campus imagery stored in the project image set for PCT Cartuja context.

#PCT Cartuja, aerospace suppliers and Andalusian digital programmes

Cartuja Science and Technology Park (PCT Cartuja) sits on Isla de la Cartuja, north of the historic centre, beside the Guadalquivir. The park concentrates startups, university technology transfer units, incubators, and offices linked to Andalusian aerospace, advanced manufacturing, and digital economy initiatives. Airbus operations near Seville San Pablo airport anchor a supplier ecosystem that publishes technical datasheets, certification statements, and recruitment microsites under tight procurement scrutiny.

Astro fits that cluster because product and employer pages compile without a default JavaScript runtime. Islands hold the pieces that genuinely need client logic: interactive capability maps for B2B engineering firms, job-board filters with export-control disclaimers, grant-application wizards, or a consent manager. Everything else stays static, which keeps Largest Contentful Paint and Interaction to Next Paint inside the bands Google uses as ranking signals when your launch collides with an aerospace trade day or a Cartuja demo sprint.

#Deliverables I ship for Cartuja and aerospace marketing buyers

  • Spanish-first product sites with English annexes for export buyers and grant evaluators.
  • Engineering wikis in MDX where counsel-owned footer YAML never lives inside author drafts.
  • Performance rescues on WordPress properties that choke mobile readers during investor roadshows.
  • Headless editorial flows (WordPress REST, Storyblok, or Sanity) feeding a static Astro public layer on Cloudflare.
  • Pre-launch audits covering Lighthouse regressions, JSON-LD shape, and consent loader order on brownfield Astro repos.

Case studies appear only with your written permission. For peer signals, use WordPress Sevilla threads or ask your procurement network for vendors who survived a Feria-week cutover.

#Heritage tourism, agri-food exporters and multilingual visitor surfaces

Seville tourism lives inside brutal seasonality tied to religious calendar peaks, fair programming, and riverfront events. Marketing wants a campaign live in days, not weeks, while operations must keep availability accurate across ticketing APIs, CRM segments, and partner wholesalers that were never designed for a static front end. Astro cannot replace a box office system, but it can publish experience landings, operator governance copy, and accessibility statements that survive crawl spikes when Feria week compresses traffic.

Agri-food cooperatives face a parallel problem: export buyers need lot traceability pages and EU labelling context, while domestic shoppers expect straightforward Spanish checkout copy. I keep heavy commerce logic inside islands or linked subdomains, and I keep statutory paragraphs in content collections validated at build time so a missing English allergen notice fails CI instead of shipping during an inspector audit window.

Visitor or buyer segmentTypical Astro surfaceCompliance touchpoint
Heritage experience guestTimed-entry landing with ES/EN copyArticle 10 organiser identification on each locale
Fair-week hospitality brandSeasonal campaign landingsArticle 21 paths on promo email capture
Aerospace procurement officerCapability brief with PDF gatesCookie taxonomy before remarketing pixels
Olive-oil cooperativeExport catalogue plus distributor portalArticle 10 footer on every locale
Cartuja coworking operatorMembership funnel in two languagesConsent before analytics on pricing pages

Multilingual funnels need explicit brief answers: which language is legally primary, whether English targets institutional buyers only or also guest packages, and whether French or German locales are contractual requirements. I map that to Astro locale folders, hreflang reciprocity on built HTML, and content collections so a missing German cancellation clause blocks release.

Plaza de España pavilion and canal.

Heritage tourism context imagery for Seville visitor funnels.

#Statutory identification and commercial messages under LSSI-CE

Spanish Ley 34/2002 (LSSI-CE) treats your Astro-built domain as an information society service. Article 10 obliges you to expose provider identity on ordinary pages: corporate name, NIF, registered address, reachable contact channels, and registry references when applicable. Seville counsel typically insist those lines stay in Spanish even on English aerospace briefs, because the Andalusian registrant remains accountable regardless of hero language.

Article 21 governs promotional outreach tied to the site: emailed offers, SMS follow-ups, and list building through onsite forms. A Feria pre-sale signup still counts as commercial communication and needs lawful basis text, honest subject lines, and one-click unsubscribe paths. Each form ships as a named partial pairing Spanish and English strings your lawyer approves once; CI blocks merge when a campaign URL lacks the matching footer linkage.

Footer data lives in Git alongside components, so compliance reviewers diff identification changes like any other release artifact instead of chasing checkboxes scattered through Elementor after a palette refresh.

TouchpointLSSI hookAstro wiring
Site-wide footerArticle 10Shared legalIdentity map injected through base layout
Supplier nurture formsArticle 21Locale-specific unsubscribe partial per list
Aerospace demo requestsTransparencyForm metadata points at active privacy policy slug
Consent UIArticle 22 + AEPDIsland blocks non-essential scripts until choice stored

Privacy policy prose stays with your DPO. Engineering delivers no analytics network calls before consent, minimal PII on lead forms, and exportable consent records when legal asks for evidence.

#Cookies, analytics, and AEPD expectations

Seville tourism and aerospace marketers still lean on the AEPD cookie guidance PDF when auditors review tag firing order. Astro’s default compile path emits HTML without client bundles; JavaScript arrives only through declared islands, which gives a clean starting point to postpone Matomo, GA4, heatmaps, and remarketing until visitors opt in.

We co-author a script inventory (strictly necessary, analytics, functional, advertising). Consent UI reads that inventory and enables imports selectively. New tracking pixels enter the repo as reviewed pull requests against the inventory, not as silent CMS injections mid-sprint.

If GA4 or Matomo stays mandatory for your board pack, implementation follows your DPO memo with compile-time or runtime guards. Acceptance testing on staging means declining cookies, hard-refreshing, confirming an empty network panel, then opting in and watching only approved endpoints on a ticketing template that still hydrates checkout islands.

#Islands architecture for fair-week traffic without SPA weight

Seville sites rarely need full single-page-application behaviour on every route. What they do need is selective interactivity:

  • Ticketing calendars that respect capacity rules without reloading the entire heritage catalogue.
  • Language toggles that persist guest choice without bloating every static paragraph.
  • Grant and RFP signups with Spanish double opt-in routed through your marketing automation stack.
  • Supplier portals with lightweight authentication islands while help articles stay static HTML.

Islands keep React, Vue, or Svelte widgets scoped per the Astro islands documentation while long-form copy stays server HTML. Screen readers encounter stable heading order, and bots receive complete paragraphs on the first response without waiting for hydration.

When an engineering unit demands Next.js for authenticated supplier dashboards, anonymous capability pages that earn organic traffic can still ship on Astro. Guadalquivir portfolios often mix static marketing on the edge with authenticated React behind SSO.

#Policy, export, and fair-season copy in collections

Cancellation rules, fair-week house policies, accessibility statements, and cooperative export FAQs belong in typed collections. Records carry lang, skuId, and translationGroup keys. Pipelines fail builds when mandatory Spanish clauses lack the English mirror your brief demands, or when hreflang files claim reciprocity that the filesystem does not support.

MDX can host maps your design studio exports, yet municipal registration codes need a cited source document. Placeholders stay marked TBD until compliance supplies authoritative text; fabricated registry numbers never ship to satisfy word-count pressure.

#Technical stack I use on Seville Astro engagements

Every repository targets current stable Astro with TypeScript strictness, Tailwind CSS design tokens from your brand PDF, and content collections for long-form pages. Deployment usually lands on Cloudflare Pages with automatic preview URLs per branch so Seville agencies can review without VPN fuss.

LayerRole on Seville sites
Astro 5.xStatic marketing and documentation routes, view transitions where brand allows
TypeScriptSchema validation on legal and export content
Tailwind CSS 4Utility layout matching supplied Figma spacing
React or Vue islandsTicketing widgets, consent, calculators
Cloudflare PagesEU-friendly edge, custom headers for security policies
GitHub ActionsLint, typecheck, Lighthouse CI on pull requests

JSON-LD mirrors the same structs: Organization with Andalusian legal address, ProfessionalService or TouristAttraction when the brief matches, WebSite listing inLanguage, and FAQPage strictly where visible FAQ markup exists. Pre-release HTML passes whichever Rich Results or schema workflow your Seville SEO partner mandates.

#Written delivery from Gdynia without a Seville desk

There is no WPPoland desk on Avenida de la Constitución and no standing Tuesday workshop inside PCT Cartuja. Work progresses through email threads or tickets, a shared Git repo, authenticated staging hosts, and sign-off lists your operations manager can forward to legal.

PhaseSeville-side participantsWhat you receive
IntakeMarketing owner, legal counsel, SEO agencyRestated scope, risk log, language map
ArchitectureIT security, DPORoute diagram, cookie taxonomy, subdomain plan
Build sprintsBrand agency, content authorsPreview URLs, diffs for legal footers
Compliance passDPO, fair operations liaison if ticketing changesEvidence pack for cookie and ID checks
LaunchDNS owner, ticketing vendorRedirect file, Search Console checklist

Central European working hours cover most Andalusian business days. Urgent production defects get written acknowledgement the same day when they block a fair campaign; feature scope still flows through change notes so procurement retains audit trail.

Fees are quoted per engagement after a written discovery pass; published ranges for senior Spanish front-end contractors vary too widely to pin a number on this page.

#Migration from WordPress or Next.js without losing Seville SEO equity

Historic Seville sites often accumulated Divi or Elementor stacks where Spanish [lssi] shortcodes appear on domestic pages but vanish on English clones. Discovery merges crawl logs, CMS exports, GA4 landing paths, and Search Console coverage into a single URL ledger tagged retain, redirect once, or retire with 410.

Content enters Git as reviewed Markdown and components, not raw SQL dumps. Builder widgets become Astro fragments with manual QA on tables lifted from PDF manuals. Lighthouse captures on Cartuja case-study templates and Alcázar campaign landings bookend the migration so marketing can show before-and-after vitals to the board.

Brochure-like Next routes shed default React payloads when they never needed client state. Authenticated engineering consoles that already rely on React Server Components can remain on Next while public catalogue HTML migrates to Astro at the CDN edge.

#Local visibility for Seville and provincia service queries

Heritage operators and aerospace SMEs win local visibility when footer NAP data matches real operations, schema types reflect actual facilities, and geo landing pages exist only for municipalities you genuinely serve beyond the registered office.

Citation-friendly AI answers benefit from semantic HTML and explicit about entities tied to sustainability or accessibility policies. Neighbourhood keyword stuffing backfires with inspectors and with readers who know the city.

#Checklist before you sign any Astro contract in Seville

Run this internally regardless of vendor:

  1. Verify Article 10 identity blocks render on ES templates and on every live guest locale.
  2. Trace Article 21 copy from each email-capture or remarketing form back to approved partials.
  3. Lock cookie taxonomy before marketing drops a GTM container ahead of Feria traffic.
  4. Document how ticketing partials expose organiser details per language.
  5. Validate reciprocal hreflang in shipped HTML, not only in a CMS admin preview.
  6. Assign a compliance owner who must approve footer diffs before merge to main.
  7. Benchmark vitals on handset profiles that match fair-week queue usage, not only office Wi-Fi.

Adjacent delivery lines on this site:

  • PHP backend developer when Laravel or Symfony should serve APIs behind Astro-rendered supplier portals.
  • Next.js developer when authenticated engineering consoles need React Server Components beyond what static Astro routes provide.
  • WordPress developer when editors keep Gutenberg workflows while Astro compiles the fast public edge.

#How to start

Email your Seville hostname, locale map, and whether you need greenfield build, migration, or vitals recovery. Replies go out on CET business days with the next written action; staging opens after scope freeze. Contracting is EU B2B with individual fees post-audit, without a Seville storefront and without cold-call discovery.

Need this service: Astro developer in Seville?

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

Describe your project

Explore other WordPress services and knowledge base