Migrate from WordPress to Astro in Aalborg
Many businesses in Aalborg 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.
I build Astro websites for companies in Aalborg and the wider Region Nordjylland whose public pages must satisfy Danish marketing law, cookie consent rules and GDPR enforcement by Datatilsynet while staying fast on mobile networks at the port, on factory floors and in airport lounges. Typical buyers are robotics and automation suppliers around the Odense Robotics hub at Aalborg University, maritime and logistics firms tied to Port of Aalborg, wireless and electronics spin-outs from AAU, and B2B manufacturers that publish bilingual datasheets and tender documents. Astro compiles each route to static HTML at build time and loads JavaScript only where an island needs it, so consent gating, signup logging and accessibility checks become reviewable template code before launch. I work alone, remotely and in writing from Gdynia in Poland, on Central European Time, the same zone as Aalborg.
What an Astro brief from Aalborg usually asks for
An Astro brief from North Jutland usually combines five requirements: Danish and English routes that stay in sync, a cookie layer that matches BEK nr. 1148 and the official cookie guidance, signup and newsletter flows that respect Markedsføringsloven § 10, marketing pages where factual claims in § 13 can be traced to documentation, and a codebase a local developer can take over after a hub hire or an AAU graduate joins the team. The sector decides which requirement carries the most weight.
- Robotics and automation firms need product pages and case write-ups that engineers trust, because buyers compare specifications before they book a demo through a form that must log consent.
- Port and logistics operators need schedules, service descriptions and contact routes that load quickly on uneven mobile coverage near terminals and industrial parks.
- University-linked startups need a site they can ship while the team is still small, with room to add MitID-backed account features later through a broker rather than inside the marketing layout.
- Established manufacturers moving off a bloated CMS need URL stability and redirect lists so search visibility survives the migration.
Your designer or agency supplies the visual design. I turn approved layouts into Astro templates, content collections and the Danish hooks for cookies, signups and accessibility.
Why robotics and automation companies in Aalborg publish on static Astro pages
Robotics and automation companies in northern Jutland publish dense specification pages, integration guides and event listings where a full client-side application adds little value. Odense Robotics, Denmark’s robotics and drone cluster, runs a regional hub in Aalborg at AAU, Niels Jernes Vej 10, 9220 Aalborg, to bring together companies, organisations and knowledge institutions through projects, networks and events (Odense Robotics, Northern Jutland hub). At a March 2023 conference with Aalborg University, the cluster described more than fifty companies in northern Jutland working in robotics, automation and drone technology, many of them high-growth firms leading in their niche (Odense Robotics, Taking Northern Jutland’s robotics industry to new heights).
That ecosystem shapes the brief. A product manager wants a new motor controller page live after a trade fair without waiting for a database cache to warm. A marketing lead wants every torque figure on the site to match the PDF datasheet the compliance team already approved. A partner manager wants English and Danish URLs that share one translation key so a missing Danish sibling stops the build instead of shipping a half-localised site.
Astro handles that material in four ways relevant to Aalborg suppliers:
- Each product family sits in a typed content collection, so a missing field for supply voltage or a broken internal link fails the build before production.
- Long-form guides and short product cards read from the same source entry, which keeps the number in the JSON-LD block aligned with the number in the visible table.
- PDF manuals and CAD links use stable paths in the repository, so partners bookmarking a datasheet keep a working URL after a redesign.
- Pages render once per deploy, so the traffic spike after a press release from the hub or a Port of Aalborg announcement hits cached HTML at the CDN edge.
Comparative advertising between competitors is common in industrial sectors. Markedsføringsloven § 21 allows comparative advertising when the comparison is objective, compares concrete documented characteristics and does not discredit a competitor’s trademarks. Section 13 requires the trader to document factual claims. I store benchmark figures and compatibility statements in typed data with a source reference field, and the component that prints a comparison refuses to render without that reference. Your counsel decides whether the statement is lawful; the template applies that decision on every locale.
How Port of Aalborg and maritime operators use Astro for public logistics pages
Port of Aalborg describes itself as one of Northern Europe’s scalable wind industry ports and as Denmark’s leading inland port, a multimodal logistics hub and an expanding business park at Vejdybet 16 and Langerak in Aalborg Øst (Port of Aalborg). Operators and tenants publish service pages, terminal information, green transition updates and contact forms where the reader may be on a phone walking a quay rather than at a desk.
Those pages favour static delivery:
- Berth availability text and PDF notices change on a schedule known to the communications team, which suits a build step more than per-request PHP.
- Image-heavy pages still need explicit width and height on figures so layout does not jump when a photo of a vessel or crane loads on 4G.
- Forms that request a quote for warehousing or towage collect commercial contact data, which triggers GDPR duties handled in the next section.
I keep interactive maps and route planners inside islands with client:visible so the rest of the page stays HTML and CSS. If the operations team later needs a live berth API, that endpoint sits behind the authenticated portal, not on every public URL.
What Markedsføringsloven changes on signup forms and B2B marketing pages
Markedsføringsloven (consolidated access via retsinformation.dk) governs marketing practices toward consumers and, in chapter 5, misleading or aggressive practices between traders. For a typical Aalborg B2B site that still sells to Danish households on a subsidiary shop, three consumer provisions matter on the marketing layer.
Section 10, stk. 1, forbids direct marketing by electronic mail, automatic calling systems or telefax without prior consent, and the trader must allow easy, free withdrawal of consent. Stk. 2 allows email about the trader’s own similar products after a sale if the customer received a clear chance to opt out when the address was collected and in every later message. Stk. 3 lists identification duties when email marketing does run: the message must be recognisable as marketing, terms must be accessible, the sender must be identifiable and an address must exist to stop further messages.
Section 5 and § 6 restrict misleading omissions on a purchase invitation, including trader identity, price and withdrawal rights where they apply. Section 13 requires documentation of factual claims at the time the marketing runs.
On an Astro build I translate those rules into template behaviour:
- The newsletter and “book a demo” forms are islands with an unticked marketing consent checkbox, plain-language purpose text and a handler that stores the consent wording and timestamp with the address.
- The soft opt-in exception for existing customers lives in your CRM rules, because the static site does not know purchase history.
- Each published performance figure or compatibility claim on a robotics page lives in a typed file with a source field, supporting the § 13 documentation duty without inventing benchmarks in prose.
- Between businesses, § 20 forbids practices likely to mislead other traders’ economic behaviour, which matters when a startup compares its cobot lineup to a larger integrator’s offer on a landing page.
Forbrugerombudsmanden supervises compliance with the consumer chapters of the act under § 25. Your legal team handles the final text; I make sure the site structure supports the duties your counsel names.
Who supervises cookies and what BEK nr. 1148 requires on an Astro site
The Danish cookie rules sit in bekendtgørelse om krav til information og samtykke ved lagring af eller adgang til oplysninger i slutbrugeres terminaludstyr, BEK nr. 1148 of 9 December 2011 (retsinformation.dk). The official guidance to that bekendtgørelse explains that the rules implement the ePrivacy storage requirement, that informed consent is needed before non-essential cookies or similar technologies run, and that technically necessary cookies are exempt (retsinformation.dk cookie guidance PDF). The same guidance states that Erhvervsstyrelsen supervises cookie rules and measures sites against the five process steps in its technical guide.
When stored or read data identifies a person, the GDPR and databeskyttelsesloven apply. Lov nr. 502 of 23 May 2018 supplements and implements Regulation (EU) 2016/679 (databeskyttelsesloven). Its § 1 states that the law supplements the GDPR, and chapter 10 establishes Datatilsynet as the independent supervisory authority. Datatilsynet’s own legislation page lists the GDPR, the Data Protection Act and related acts as the framework it works within (Datatilsynet legislation).
On an Astro site aimed at Aalborg readers I keep the split explicit in code:
- The base layout ships no third-party analytics, chat or advertising scripts.
- A single consent island mounts optional trackers only after accept or reject, with equal visual weight on both actions, matching the guidance emphasis on genuine choice.
- A build step scans generated HTML for known tracker hostnames outside the consent island and fails the deploy when it finds one.
- The privacy page lists the same processors named in a typed config file beside the forms, and a test compares the two lists.
- For information society services offered directly to children, databeskyttelsesloven § 6, stk. 2, sets age 13 for a child’s own consent to processing based on consent; younger children need parental authority.
Self-hosted fonts and locally built CSS avoid leaking visitor IP addresses to third-party asset domains, which simplifies both the cookie layer and the GDPR processor list your data protection contact maintains.
What the European Accessibility Act changes for Danish e-commerce on Astro
Directive (EU) 2019/882 on accessibility requirements for products and services (EUR-Lex 2019/882) applies to several consumer services after 28 June 2025, including e-commerce services as defined in Article 2(1)(f). Recital 42 describes e-commerce as a service provided at a distance through websites and mobile device-based services at the individual request of a consumer with a view to concluding a consumer contract.
Many Aalborg industrial firms sell only B2B on the main domain but run a small spare-parts shop for Danish consumers. Where that shop falls in scope, I build the checkout and product templates with:
- Semantic headings and landmarks on product, basket and checkout routes.
- Visible labels and error messages on form fields, not placeholder-only inputs.
- Keyboard focus order that follows the visual sequence on consent dialogs and checkout steps.
- Text alternatives for product images that matter to the buying decision.
Annex I functional requirements and harmonised standard references belong in your accessibility statement; I deliver templates and automated checks that your accessibility lead can sign off. Member States may delay certain obligations under Article 4(8) until 28 June 2027; your counsel confirms whether that derogation applies to your service category.
When MitID belongs on the site and when it does not
MitID is Denmark’s national digital ID. Digitaliseringsstyrelsen explains that service providers use MitID through certified brokers, and that only certified brokers access MitID identities (DIGST, Til brokere). NemLog-in acts as a MitID broker: it is the central user-management entry when people log into public digital self-services with MitID or MitID Erhverv, and more than five hundred digital services use it (DIGST, Om NemLog-in). Organisations must use NemLog-in when the digital self-service performs a public authority task or requires secure authentication under the MitID law; in other cases they may choose an approved broker. Private organisations may connect to NemLog-in as a broker for a fee without single sign-on when the system is not used for authority tasks.
For an Astro marketing site in Aalborg this split matters:
- Public product pages, case studies and fair landing pages do not embed MitID buttons as decoration or false trust signals.
- Customer portals, distributor ordering tools or warranty registration that genuinely need MitID integrate through a broker contract your security team negotiates, often on a subdomain separate from the static marketing origin.
- MitID Erhverv for company representatives follows the same broker pattern; it is not a drop-in script tag on a brochure page.
I document the boundary in the handover note so the next developer knows which routes are static marketing and which URL fronts the broker-backed application.
How Aalborg University spin-outs keep WordPress and still ship Astro
Aalborg University lists its main address at Fredrik Bajers Vej 7K, 9220 Aalborg Øst (Aalborg University). Spin-outs and research groups often start with WordPress because editors already know it. A headless split keeps that workflow while the public domain serves Astro output:
- Editors draft in WordPress; published posts trigger a build webhook.
- Astro fetches only public post types and builds static routes for news, team pages and publication lists.
- The WordPress admin sits on a hostname that is not linked from public navigation, which reduces brute-force noise on the CMS.
Content collections can mirror the same schemas when the team later moves authoring into Git or a headless CMS. The important part for a young AAU-linked firm is that the first launch does not lock them into a theme marketplace they cannot audit.
Which technical scope an Aalborg Astro project covers
An Aalborg Astro project covers the public website layer: routing, content models, templates, performance, structured data and the Danish compliance hooks above. A typical scope includes:
- Danish (
da) and English (en) routes with Astro’s internationalization routing and reciprocal hreflang from shared translation keys (Astro internationalization). - Core Web Vitals checked against the thresholds documented on web.dev vitals.
- Islands for calculators, configurators and consent UI, using partial hydration (Astro islands).
- An editorial backend that fits your team: Markdown in Git, a headless CMS or WordPress as described above.
- Deployment to the host your security policy names, because the build output is static files.
- Cookie, signup and accessibility hooks wired before launch.
When Astro is the wrong choice for an Aalborg company
Astro is the wrong choice when most of the value sits behind a login with per-user state on every screen, such as a live fleet dashboard for mobile robots or a customer-specific spare-parts contract portal. A framework built around server rendering and client state fits that work better; for those cases see the Next.js developer Aalborg page. Astro is also unnecessary when an existing WordPress site already meets performance targets and the editorial team depends on plugins you cannot replace yet. I state that conclusion in the written estimate when a brief points that way.
How an Aalborg Astro project runs from brief to launch
| Stage | What you receive | What I need from your team in Aalborg |
|---|---|---|
| Brief review | A free initial written estimate with scope, assumptions and open questions | Current site URL, launch languages, owner of design files, which Danish rules your counsel flags |
| Architecture note | Route map for da and en, content schemas, redirect list, third-party script inventory | Confirmation of slugs, processors and consent categories |
| Build | Staging deploys from pull requests and a changelog in Git | Approved designs and content, or marked placeholders |
| Compliance pass | Consent island, tracker scan, signup consent logging, accessibility checks on in-scope templates | Legal texts, privacy notice, cookie policy |
| Launch | DNS checklist, redirect file, handover guide | A named contact for DNS and a go-live date |
Communication runs by email, pull request comments and your issue tracker on Central European working days. I do not travel to Aalborg for on-site workshops.
Related services in Aalborg
- Next.js developer Aalborg for logged-in portals and applications with per-user state.
- Migration to Astro and Next.js in Aalborg for moving an existing site off a monolithic CMS.
Send an Aalborg project brief
Send the brief through the contact form with your current site URL, the languages you need at launch, which Danish rules your counsel applies (B2B marketing, consumer shop, broker-backed login), who supplies the design, and your target launch window. I reply on Central European working days with questions or a written scope, and the opening quote stays free after I have read the brief.
Selected projects
Examples of my work.
Vector Solutions - Telecommunications Technology Pioneer
Vector Solutions is a company recognized in Poland and throughout Europe as a pioneer in the technology sector, transforming modern communication with innovative solutions for cable operators and telecommunications companies.
Victim Assistance Office - odszkodowania.pl
The Victim Assistance Office website was designed to provide professional and empathetic information to support people in difficult life situations. The site...
Website Delivery: Sole Practitioner Law Firm
Technical implementation for a sole practitioner law firm in Wroclaw: WordPress migration, SSL certificate, mail server configuration, and pre-launch QA.
WordPress support & development in Aalborg
See also in Denmark
Need this service: Astro developer in Aalborg?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
WCAG 2.2, BFSG, EAA conformance report and remediation backlog.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Custom WordPress engineering and architecture.
Clearer structure, messaging, and conversion flow.
Core Web Vitals, caching, and faster delivery.
NIS2 and DORA scope mapping, supplier register, incident runbook.
Related categories
Supporting articles

Germany's Barrierefreiheitsstärkungsgesetz applied from 28 June 2025. It transposes EAA Directive 2019/882 into national law. I unpack how it affects WooCommerce stores in DE and the four plugin failure patterns I see in audits.

WCAG 2.2 was first published as a W3C Recommendation on 2023-10-05; the current published version on www.w3.org/TR/WCAG22/ is dated 2024-12-12. The EU Accessibility Act (Directive 2019/882) applies from 2025-06-28. Germany's Barrierefreiheitsstärkungsgesetz transposes it into federal law on the same date. This article is the implementation map for a WordPress site in 2026.

BFSG and the EU Accessibility Act require a published accessibility statement with a working complaint mechanism, not just a compliant front end. This is a copy-ready template structure mapped to EN 301 549 clauses and WordPress deliverables.