A block theme of your own
Editor blocks coded in your brand style: headers, service cards, galleries, price tables. Your team builds new pages without a page builder and without breaking the mobile view.
WordPress is known as both easy and insecure, and which one you get depends on who builds it. One install can be a lean site the receptionist updates in two minutes; another can be a tangle of plugins nobody has dared touch since 2021. The outcome is settled before anything is installed, by a few plain answers: what your team will publish each week, which languages you need, whether you will sell, and who will apply updates. Take a gestoría in Valencia wanting pages in Spanish and Valencian, a tax news blog and an appointment form. With those answers written down, the whole project fits into eight plugins and a theme of its own.
Here is what a WordPress site built by Apply contains, item by item. Anything missing from this list only goes in with a written reason.
Editor blocks coded in your brand style: headers, service cards, galleries, price tables. Your team builds new pages without a page builder and without breaking the mobile view.
Separate accounts for writing, reviewing and administering. Drafts wait for approval, and nobody without rights can touch plugins or settings.
Spanish plus Catalan, Valencian, Galician or Basque through WPML or Polylang, each with its own URLs and correct hreflang. English is added when you serve clients abroad.
A shop with Redsys, Bizum and Spanish carriers only if the site is going to sell. No planned sales, no shop module.
Forms with the GDPR notice, spam protection without irritating captchas and, where useful, appointment booking linked to Google Calendar or Microsoft 365.
A legal notice under the LSSI-CE, a privacy policy and a cookie banner that holds analytics back until consent, in line with AEPD guidance.
Caching, WebP images, two-factor sign-in for admins, login attempt limits and daily off-server backups from day one.
Two things set the pace: how many distinct templates the site needs and when the copy is ready. Coding the block theme is rarely what holds things up.
Before any talk of design, we list what your team publishes now and what it wants to publish: news, product sheets, vacancies, events. That list tells us which blocks to build.
The editor pieces are designed and coded on staging. You try them out by assembling two or three real pages before approving them.
Migrated or fresh content, forms wired to your mailbox or CRM, languages paired up and, for shops, test payments through Redsys and Bizum.
Go-live with 301 redirects, accounts transferred to your company, a training session by video call and a document stating who updates what, and how often.
A premium plugin whose licence has lapsed stops getting security fixes, even though it keeps working. It is one of the most common situations on small-business WordPress sites: the form builder or SEO plugin was bought three years ago on the card of someone who has since left, the renewal failed and nobody noticed. So every licence is registered to the company under a shared mailbox, and its renewal date goes into the handover document.
Yes, provided someone maintains it. Core gets patched regularly; the real risks are abandoned plugins, weak passwords and updates nobody installs. Keep the component list short, put two-factor sign-in on admin accounts and name a person responsible for updates, and WordPress is as safe as any comparable platform.
That depends on how it was built. A light theme with current plugins can be reworked section by section. If everything hangs off a heavy page builder or a discontinued theme, a new theme reusing your copy, images and URLs usually works out cheaper. We inspect the installation before quoting.
As many as you need. WordPress separates roles: writers, editors who review and publish, and administrators. A law firm might let every lawyer draft articles while only one person publishes them, so settings never get changed by accident.
Not necessarily. What matters is that the banner genuinely blocks non-essential cookies until the visitor agrees, and that saying no is as easy as saying yes, as the AEPD expects. Free tools can do that; paid ones add consent logging. We choose according to what the site actually loads.
Nothing changes. The code follows WordPress standards, the accounts belong to your company and the handover document explains how everything fits together, so another professional can carry on without asking anyone's permission. While we work together, technical time is billed at €75 per hour + VAT or covered by a Start, Business or Premium plan.
Explain what the site should deliver and which tools your business relies on already. Expect a realistic schedule in return, plus the plugins we would propose.
Your request is with us
Expect an answer within one working day. A reported fault that has halted your team is handled first.
No match found. Try another spelling, or go with the closest provincial capital: every job is done remotely, so the location makes no difference to what we deliver anywhere in Spain.