Migrate from WordPress to Astro in Oslo
Many businesses in Oslo 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 Oslo companies whose public pages carry claims a regulator can check: renewable energy developers publishing project data in Norwegian and English, fintech teams marketing a product under Finanstilsynet supervision, and software startups growing out of Mesh and Oslo Science Park. Astro renders each route to static HTML at build time and loads JavaScript only for the components that need it, so the consent rules Datatilsynet enforces and the sales rules in angrerettloven and markedsføringsloven become template code a reviewer can read in Git before launch. I work alone, remotely and in writing from Gdynia in Poland, on the same Central European Time as Oslo.
What an Astro brief from Oslo usually asks for
An Astro brief from Oslo usually combines four requirements: Norwegian Bokmål and English routes that stay in sync, a tracking setup that would survive a Datatilsynet inspection, checkout or signup flows that follow Norwegian consumer and marketing law, and a codebase the client’s own developers can take over. The sector decides which of the four carries the most risk.
- Renewable energy and grid technology companies need accurate data, because investors and journalists quote their capacity figures, project status and report PDFs.
- For fintech and payment teams the risk sits in marketing claims: an interest rate example or a fee illustration on a landing page is a statement under markedsføringsloven.
- Software startups from the Oslo coworking and research clusters ask for fast iteration and a handover their first in-house frontend hire can follow.
- Consumer brands selling online to Norwegian households care about the checkout, where angrerettloven decides whether an order binds the buyer at all.
Your designer or agency supplies the visual design and the wireframes. I turn approved layouts into Astro templates, content models and the Norwegian hooks for consent, checkout and signups.
Why clean energy companies in Oslo publish project data on static pages
Static pages suit clean energy publishers because project content changes through reviewed decisions, and a build step is a natural checkpoint for each decision. Statkraft, which describes itself as Europe’s largest renewable energy producer, runs its global headquarters from Lilleaker in Oslo (Statkraft, about the company). Energy companies of every size in the region publish similar material: project registries with capacity and location data, sustainability reports as PDFs, supplier requirements, and press releases that go out in Norwegian and English on the same morning.
Astro handles that material in four ways:
- Each wind, solar or hydro project is one entry in a typed content collection, so a missing capacity field or an unknown status value stops the build before it reaches the live site.
- The same entry feeds the project page, the project list, the RSS feed and the JSON-LD block, so the figure in the structured data matches the figure a reader sees.
- PDFs and images live in the repository under fixed paths, so links to an older sustainability report keep working after a redesign.
- Every page is rendered once per deploy, so the traffic spike after a licence decision or a quarterly report lands on CDN-cached HTML instead of a database.
A status change from “consent application” to “under construction” becomes a one-line edit in a pull request, with the reviewer and the date recorded in Git. For a communications team that answers to auditors on sustainability reporting, that history shows who changed a published figure and when. Norwegian and English versions of each project share one translation key, and the build fails when the English page exists without its Bokmål sibling.
How fintech marketing pages in Oslo stay inside markedsføringsloven
Fintech marketing pages in Oslo stay inside markedsføringsloven when every factual claim has a documented source and every commercial message is recognisable as one. The Marketing Control Act (markedsføringsloven, LOV-2009-01-09-2) applies to the public site, and its § 35 gives Forbrukertilsynet supervision of the first five chapters. Three sections shape the copy directly:
- § 3 requires the advertiser to hold documentation for factual claims at the time the marketing runs.
- § 7 treats incorrect or misleading information about a product’s main features, its price, the trader’s status or consumer rights as a misleading practice.
- § 8 makes a practice misleading when it hides its commercial purpose and the context does not reveal that purpose.
In an Astro build I keep every interest rate example, fee illustration and performance figure in one typed data file. Each value carries a source reference and an approval field, and the component that prints a number refuses to render without both. The Git log then links each published figure to the document behind it, with a date, which makes the documentation duty in § 3 easier to meet. Your legal team decides what is lawful, and the template applies that decision on every page that shows the figure.
Finanstilsynet’s regulatory sandbox and the word “approved”
Finanstilsynet runs a regulatory sandbox for fintech with rolling admission, open to existing financial firms, new providers of financial services and technology vendors that serve supervised firms (Finanstilsynet, regulatory sandbox). The regulator states that admission is neither an approval nor a quality assessment of the product, technology or service. A landing page that turns sandbox admission into “approved by Finanstilsynet” contradicts that wording, and § 7 of markedsføringsloven covers misleading statements about a trader’s status. I flag that kind of phrase in the copy review and leave the final wording to your counsel.
The logged-in product usually stays in its own stack, such as a Next.js application or a native mobile app. Astro takes the public layer around it: product pages, fee explainers, help articles and the careers section, all of it static and quick to review.
What the Datatilsynet tracking pixel inspection means for an Astro build
The Datatilsynet tracking pixel inspection means every third-party script on an Oslo site needs a legal basis, honest information and a neutral consent choice before it loads. In 2025 the authority inspected six Norwegian websites and found that all six shared visitor data with third parties without a legal basis and broke the duty to inform visitors (Datatilsynet, tracking pixels on six websites). The sites included an online pharmacy, a medical services provider, a health information site and a helpline for children run by Kristiansand municipality. The helpline received an administrative fine of NOK 250,000, and the other five received reprimands. Datatilsynet described it as its first inspection of this type and said future sanctions may be much stricter.
Among the practices Datatilsynet listed were telling visitors they were anonymous, sharing special category data and children’s data, nudging visitors towards consent and giving misleading consent information.
The legal frame comes from two acts. The Personal Data Act (personopplysningsloven, LOV-2018-06-15-38) gives the GDPR effect in Norway, and its § 20 names Datatilsynet, which is based in Oslo, as the supervisory authority. Its § 5 sets 13 as the age at which a child can consent alone to information society services, which matters for youth savings apps and other consumer products aimed at teenagers. Section 3-15 of the Electronic Communications Act (ekomloven, LOV-2024-12-13-76), in force since 1 January 2025, requires informed consent at the GDPR standard before a site stores or reads information on a visitor’s device, with exceptions for strictly necessary storage.
On an Astro site I translate that frame into five build rules:
- The base layout contains no third-party script, and analytics, chat widgets and advertising pixels mount from a single consent island after the visitor makes a choice.
- The accept and reject buttons share the same size, weight and position level, because nudging towards consent was one of the practices Datatilsynet listed.
- A build step scans the generated HTML for known tracker domains outside the consent island and fails the deploy when it finds one.
- Forms send only the fields their stated purpose needs, and a typed config file lists every processor that receives form data, so your data protection officer can diff it.
- The privacy page names the same processors as that config file, and a test compares the two lists.
A static Astro site has no database or admin login on the public server. The realistic breach paths are form endpoints, third-party scripts and API keys leaked through the build pipeline. Datatilsynet expects a breach report within 72 hours through its Altinn form and accepts follow-up information in stages (Datatilsynet, reporting a breach). I document each data path at handover, so the person filing that report knows what every form collected and where it went.
What a Norwegian checkout has to show under angrerettloven
A Norwegian checkout has to show the core contract terms right before the order, label the order button as a payment obligation and explain the 14-day right of withdrawal. The Cancellation Act (angrerettloven, LOV-2014-06-20-27) sets these duties for distance sales to consumers:
- § 8 lists the information the trader gives before a distance contract, including the right of withdrawal, its conditions and deadlines, and a standard withdrawal form (angreskjema).
- § 16 requires key terms to appear just before the order and the order button to read “bestilling med forpliktelse til å betale” (an order with an obligation to pay) or equivalent wording, and a consumer is not bound when the trader skips this.
- § 21 sets the withdrawal period at 14 days, counted from the contract for services or from the day the consumer receives the goods.
- § 21 also extends that period by up to 12 months when the trader never gave the withdrawal information.
In Oslo these rules reach any company that sells to households online, for example a home EV charger installation, a rooftop solar package or a subscription service. I keep the order button label as one Norwegian string in the codebase, and an end-to-end test checks the exact wording on the built checkout page, so a redesign cannot swap it for a generic label such as “Fullfør” (complete). Where the payment step runs in Shopify, Stripe Checkout or a Nordic payment provider, Astro renders the product pages and the pre-contract summary, and I check the hosted step’s button label against the same string before launch.
The angreskjema ships as a static HTML page and a PDF, linked from the order confirmation template and from the footer. Under § 20 the consumer may also withdraw by any other unambiguous statement, so the customer service inbox counts as a valid channel and the withdrawal page says so.
Which Norwegian rules apply to newsletter and SMS signups?
Section 15 of markedsføringsloven applies to newsletter and SMS signups: marketing to private individuals by email, SMS or MMS requires their prior consent. The act counts text and multimedia messages to mobile phones as electronic mail. One exception covers existing customers whose address the trader collected in connection with a sale, limited to the trader’s own similar products, and only when the customer can opt out simply and free of charge when the address is collected and in each later message. Forbrukertilsynet can impose an administrative fine under § 42 for significant or repeated breaches of § 15.
On an Astro site the signup form is a small island with an unticked consent checkbox, a plain-language purpose text and a submission handler that stores the consent wording and a timestamp with the address. The existing-customer exception lives in your CRM or email platform rules, because the website cannot know who bought what. When a Norwegian and an English signup form both exist, they send the same consent version identifier, so a later audit can match each address to the exact text that person saw.
Who maintains an Astro site in Oslo after launch?
The developer who maintains an Oslo Astro site after launch is usually a frontend or full-stack engineer on the client’s own team. Developers who could take over such a codebase meet at a few Oslo hubs:
- Mesh runs Mesh Nationaltheatret at Tordenskiolds gate 2 and Mesh Youngstorget at Møllergata 6 and 8, and describes its Nordic community as more than 5,000 members strong, with developer events such as Agent Meetup Oslo on its calendar (Mesh Community).
- Oslo Science Park at Gaustadalléen 21 reports more than 300 organisations on site, 190 of them startups, alongside University of Oslo programmes such as UiO iHub (Oslo Science Park).
- Oslo Innovation Week, owned by the City of Oslo and run by Oslo&Co, brings founders and investors to the city each October (Oslo Innovation Week).
I write the codebase for that next developer:
- TypeScript throughout, following Astro’s documented conventions for routing, content collections and islands.
- No private framework, custom compiler plugin or build step that only I can explain.
- A README with the commands to run the site locally, add a page, add a language and deploy.
- The repository, the deploy pipeline and the DNS settings in your company’s accounts from the first day.
- A redirect file in plain text and a short guide for editors.
Before handover I apply one test: a developer who has read the Astro documentation and nothing else can add a page in Bokmål and English without asking me.
Which technical scope does an Oslo Astro project cover?
An Oslo Astro project covers the public website layer: routing, content models, templates, performance, structured data and the Norwegian compliance hooks above. A typical scope includes six parts:
- Norwegian Bokmål (
nb) and English (en) routes built with Astro’s internationalization routing, with reciprocal hreflang generated from a shared translation key (Astro internationalization guide). - Core Web Vitals checked against the thresholds Google publishes on web.dev, meaning LCP up to 2.5 seconds, INP up to 200 milliseconds and CLS up to 0.1, measured on mobile profiles.
- Interactive islands for the parts that need JavaScript, such as a savings calculator, an energy price chart or a booking form, written in React, Svelte or Vue (Astro islands).
- An editorial backend that fits your team, whether Markdown in Git, a headless CMS, or WordPress kept as the authoring tool with Astro serving the public domain.
- Deployment to Cloudflare Pages or to the host your security policy names, since the build output is plain static files.
- Universal design built into components, because Norway’s regulation on universal design of ICT covers a company’s main web solutions aimed at users, while internal tools that staff use at work fall outside it (forskrift om universell utforming av IKT-løsninger).
When is Astro the wrong choice for an Oslo company?
Astro is the wrong choice when most of the site sits behind a login. A customer portal for a power retailer, a trading dashboard or a banking app holds per-user state on every screen, and a framework built around server rendering and client state fits that work better, as described on the Next.js developer Oslo page. Astro is also unnecessary when a WordPress site already passes Core Web Vitals and the editorial team depends on its workflow, and then WordPress developer Oslo is the better starting point. I state that conclusion in the written estimate whenever an Oslo brief points that way.
How an Oslo Astro project runs from brief to launch
An Oslo Astro project runs in five written stages, with a staging URL that Norwegian and English reviewers can open at any point.
| Stage | What you receive | What I need from your Oslo team |
|---|---|---|
| Brief review | A free initial written estimate with scope, assumptions and open questions | Current site URL, launch languages, target launch window, owner of the design files |
| Architecture note | Route map for nb and en, content schemas, redirect list, inventory of third-party scripts | Confirmation of slugs, processors and the consent categories your data protection officer uses |
| Build | Staging deploys from every pull request and a changelog in Git | Approved designs and content in both languages, or clearly marked placeholders |
| Compliance pass | Consent island, tracker scan, order button test, signup consent logging | Legal texts from your counsel, angreskjema wording, privacy notice |
| Launch | DNS checklist, redirect file, Search Console checks, handover guide | A named person for DNS and a go-live date |
Communication with Oslo teams runs by email, pull request comments and the issue tracker you already use. I do not travel to Oslo or run on-site workshops, replies come on CET working days, and every decision ends up in writing.
Related services in Oslo
- Next.js developer Oslo for logged-in portals and applications with per-user state.
- Migration to Astro and Next.js in Oslo for moving an existing Oslo site off WordPress, Joomla or an older framework.
- WordPress developer Oslo for Oslo teams that keep WordPress as their main platform.
- PHP developer Oslo for Laravel or Symfony backends behind an Astro frontend in Oslo.
Send an Oslo project brief
Send the brief through the contact form with your current site URL, the languages you need at launch, the Norwegian rules that apply to you (consumer sales, financial marketing, health data), who supplies the design, and your target launch window. I reply on CET working days with questions or a written scope, and the first written estimate for an Oslo project is free.
Selected projects
Examples of my work.
Corporate Website: osemka.pl - Banner
A package of various special banners for the osemka.pl website
Corporate Website: osemka.pl - bannery
A package of various special banners for the osemka.pl website
Corporate Website: strefapremium.pl
The website strefapremium.pl has been designed as a modern premium portal, dedicated to users seeking exclusive content and services. The site combines high-...
WordPress support & development in Oslo
See also in Norway
Need this service: Astro developer in Oslo?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
Migration to Astro, Next.js, and headless WordPress.
WooCommerce sync with ERP and wholesale systems.
Business process automation around WordPress and company systems.
Library of concrete automation use cases.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Related categories
Supporting articles

Six to sixteen weeks for typical engagements, with a four-phase shape: discovery, scoping, build and cutover, tuning. The variables are catalogue size, integration count, URL preservation, and editorial team readiness, not framework choice.

A definitive 4-year Total Cost of Ownership (TCO) analysis, real-world Core Web Vitals benchmarks, Astro 7 GraphQL APQ architecture, and a 10-point executive decision matrix for choosing between decoupled and traditional WordPress.

The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.