We are not just a remote agency. We are an active part of the ecosystem. We believe in Open Source and contributing back to the community that powers over 40% of the web (W3Techs).
In Lyon's competitive market, site speed is your strongest SEO asset. Our Astro + Headless WP stack delivers performance that leaves competitors behind.
For businesses in Lyon serving Local SMB and Enterprise, data security is paramount. Headless architecture virtually eliminates standard WordPress attack vectors.
A WordPress site serving businesses in Lyon sits in Part-Dieu, in a Confluence office or in a Gerland laboratory. That proximity does not turn a marketing site into a congress booking platform for Centre de Congrès. It does mean updates, backups, consent plugins and form integrations are discussed before the first production change, not as an appendix after an incident that triggers a question from legal about GDPR and the Commission Nationale de l’Informatique et des Libertés (CNIL).
WPPoland delivers ongoing WordPress maintenance from a senior Polish team for businesses, laboratories and organisations with a base, branch or client base in Lyon and Métropole de Lyon. Scope is WordPress maintenance: tested updates, daily backups, security and performance monitoring, incident response under a written SLA, and up to four hours of small development changes per month. Custom theme builds and plugin development are separate topics, described on the WordPress developer in Lyon page.
Lyon is France’s second-largest economic centre after Paris: a chemical and pharmaceutical tradition, biotechnology in Gerland, logistics along the Rhône and a growing digital ecosystem around Confluence and Lyon Digital Hub. This is not Paris fintech or the Côte d’Azur tourist market. Here WordPress often serves B2B catalogues, employer-branding portals, laboratory enquiry forms or product pages for Part-Dieu firms that must survive a plugin update in the same week a lawyer asks about EU hosting and CNIL consent for cookies.
Part-Dieu is France’s second-largest business district after La Défense. Towers, Gare de Lyon-Part-Dieu, conference hotels and corporate offices create a context where WordPress holds product landings, demo forms, technical blogs and employer-branding pages. A plugin update breaking a form or an FR/EN translation regression hurts during a Part-Dieu congress week or before an investor meeting, not in August. Maintenance in Lyon must respect those windows, not treat every Tuesday as equal.
Confluence is the district south of Lyon, around Musée des Confluences and a newer startup ecosystem. Lyon Digital Hub and communities such as Silicon Rhône meet in this area. WordPress serves SaaS landings, beta registration forms, product blogs and FR/EN multilingual content for firms selling across the European Union. A maintenance brief from a client here often sounds like: “we have Elementor, editorial is scared of updates, and the CTO wants tested staging and Git”. That is an operations and process problem, not a marketplace template problem.
Gerland and the Lyonbiopôle biotechnology park are a different profile from a Part-Dieu corporation. More regulatory content, more PDF documents, more forms collecting personal data under GDPR and more audit-trail requirements. WordPress in this environment is a research portal, laboratory services catalogue or spin-off site that collects enquiries and must respect France’s Loi Informatique et Libertés and CNIL guidance. A consent log that disappears after a plugin update is a compliance incident, not a UX ticket.
The chemical and industrial sector in the Lyon metropolitan area generates another profile: parts catalogues, quotation request forms, distributor pages and FR/DE content for cross-border clients from Alsace or Switzerland. WordPress must survive a traffic spike after a new product line announcement, not just look good on a laptop in a Part-Dieu office.
The typical brief that reaches maintenance in Lyon does not read “keep it updated somehow”. It reads: last Core update was eight months ago, backup plugin shows green but nobody has restored since 2022, WPML or Polylang serving French text on the English version after a patch, and a new congress subpage broke because someone updated a page builder without staging. That is technical debt that surfaces on a Monday morning, not in an SEO audit.
WPPoland is not a contractor for Métropole de Lyon or a Part-Dieu tower management company. Proximity to France’s second business district sets the bar for documentation, roles and FR/EN bilingual delivery. It does not set a list of corporate references.
Maintenance in Lyon is a written SLA, not a vague “we look after the site”. The monthly package covers:
Pricing is individual and delivered in writing after scope is agreed. There is no rate card on this page.
Every engagement in Lyon starts with an onboarding audit, usually about one hour on the live install plus follow-up on staging setup. The audit documents:
| Area | What is checked |
|---|---|
| Plugin inventory | active plugins, last update dates, known CVEs, overlap with consent and cache layers |
| Hosting | PHP version, memory limits, object cache, TLS, CDN, EU residency if contract requires it |
| Backups | schedule, retention, last successful restore test, off-site copy |
| Security | admin accounts, 2FA, file permissions, XML-RPC, file editor, secrets in Git |
| FR/EN setup | WPML or Polylang configuration, hreflang, broken language pairs, string sync |
| Performance | Lighthouse baseline on homepage, CPT archive and a representative landing in both languages |
| Compliance hooks | consent plugin behaviour, form data flows, log retention, politique de confidentialité links |
Inherited installs are common. The first month often involves more remediation than routine maintenance: patching vulnerable plugins, fixing broken backups, removing malware, stabilising an FR/EN pair that drifted apart, or moving secrets out of wp-config.php in Git history. Remediation is listed with priorities before steady cadence begins. Steady maintenance does not start on a site where restore has never been verified.
The most expensive maintenance failure in Lyon is not a missed minor plugin update. It is a Core or major plugin update pushed to production on a Thursday because “it looked fine on localhost”, breaking the English version of a Part-Dieu product landing the day before a B2B campaign for the French and German markets.
Staging is a production copy with anonymised data. WP-CLI search-replace on URL, separate keys, crons that send mail to real addresses disabled. Editorial and IT click through staging with real Gutenberg patterns in both languages, not on the developer’s laptop. Multilingual regression, form submission, consent banner behaviour and keyboard navigation happen here.
Production promotion is a documented step: tag or merge, asset build, cache warmup, rollback path to the previous tag. The team does not “quick upload” one PHP file over SFTP, because nobody can reconstruct what was on production on Friday before a congress week in Part-Dieu.
Update cadence follows risk, not calendar superstition. Security patches for actively exploited CVEs move faster than cosmetic plugin updates. Major version jumps (PHP, Core, WooCommerce if present) get their own written plan and acceptance criteria. WooCommerce stores are a separate scope; if the brief includes checkout, see WooCommerce developer in Lyon.
Congress events in Part-Dieu, trade fairs at Eurexpo or product campaigns targeting the French and German markets create windows where hundreds of firms watch product landings, registration forms and CRM integrations. A site failure mid-congress week is not a “bug for the backlog”. It is lost leads and reputation damage with partners who have a full calendar for the quarter.
The maintenance runbook for clients in Lyon includes a production deploy freeze for campaign windows, usually from two weeks before an event until one week after. Critical security updates go through staging and a night window; everything else waits. That is not a developer preference. It is an operational decision agreed with the client before the season. Anyone doing a “small cache patch” on congress Monday learns when the site does not survive the traffic spike from attendees’ phones.
Hosting “in the EU” is a jurisdiction argument in procurement, not a magic shield. A form collecting personal data without legal basis is not fixed by a server in France alone. Maintenance still records where backups live, whether off-site copies cross borders, and what the client’s processor agreement requires.
Practical backup rules written into the runbook:
If the client requires backups to remain in France, that is a contract topic checked at onboarding against the actual provider configuration (OVH in France, Scaleway in Paris, AWS eu-west-3 in Paris, Claranet in Lyon), not an assumption from the TLD.
France applies GDPR alongside the national Loi Informatique et Libertés. The supervisory authority is the Commission Nationale de l’Informatique et des Libertés (CNIL). For WordPress maintenance in Lyon that is not an abstract legal paragraph. It is decisions in forms, consent plugins, politique de confidentialité and audit logs after every update cycle.
Posture maintainable in code and process:
What maintenance checks after updates that touch compliance:
CNIL publishes recommendations on cookies and tracking that affect GTM, Meta Pixel and similar tools. A consent plugin copied from a German shop is not automatically CNIL-aligned, and no banner is not automatically legal when tracking runs. WPPoland does not sell legal opinions. Maintenance ensures tools on the site match what stands in the politique de confidentialité, and that after a GTM or consent-plugin update consent logs still record correctly.
If a personal-data breach requires notification to CNIL, logs and the incident timeline must fit a notification workflow. WPPoland documents interventions with timeline, root cause and remediation steps. It does not file on behalf of the data controller.
The most common post-update regression in Lyon is not PHP fatal errors. It is the English version showing French strings because a plugin update reset language mappings or because someone edited the FR page and the EN copy was never synced.
Maintenance for bilingual sites in Lyon includes:
WPML and Polylang solve hreflang and language copies. They do not solve process: who approves French text, who approves English, before production. The maintenance runbook records whether approval sits with the client in Lyon, with the Polish content lead, or both in parallel.
Monitoring combines synthetic uptime checks, application-level alerts and security scanning. Alerts route to Slack and email with enough context to triage without logging into five dashboards.
Incident management follows ITIL-lite: detection, triage, resolution, post-mortem. Every confirmed incident gets a root cause summary within 48 hours. SLA compliance is tracked against the contracted uptime tier, with monthly reports surfacing target and actual rather than a marketing number.
Priority tickets: sub-four-hour response on weekdays. Confirmed security incidents and production outages: response outside hours where the SLA covers it. The intervention is logged with timeline, containment steps, remediation and follow-up risks. That log is what legal and IT in Lyon need when asking “what happened between 14:00 and 16:30 on Tuesday”.
Communication runs through a written ticketing channel. Calls unblock decisions; they do not replace the audit trail.
Speed in Lyon is not vanity. B2B firms and life-sciences organisations compete on credibility; a site that loads in four seconds on mobile loses form completions and signals neglect to reviewers accustomed to Part-Dieu project standards.
Performance maintenance includes:
Performance budgets are set at onboarding and checked against lab and, where available, CrUX field data. Regressions after updates are caught on staging, not discovered by the client on Monday morning before a seasonal campaign.
Maintenance is the steady state after launch, or the rescue lane for a site that outgrew DIY updates. If the site needs a new block theme, custom plugin or large refactor, scope moves to WordPress developer in Lyon. If the site needs checkout, Payplug integration or product catalogues, scope moves to WooCommerce developer in Lyon.
Development engagements end with a runbook: how to add a pattern, how to ship a branch, how to rebuild staging, whom to call when the editor will not save. Maintenance picks up that runbook and keeps it current as Core, plugins and hosting evolve. A handover without a runbook is a support ticket waiting to happen.
Lyon Digital Hub and communities such as Silicon Rhône are reference points for Lyon’s digital ecosystem: meetups, networking, projects linking administration, startups and IT suppliers in Confluence. They are not a WPPoland sales argument. They are a barometer: editorial and IT teams in Lyon ask about restore tests and staging because they heard those questions at local meetups and in corridors near Musée des Confluences.
The chemical and pharmaceutical tradition along the Rhône, plus Lyonbiopôle in Gerland, add reviewers who read monthly reports, not only marketing copy. A laboratory that loses CNIL consent logs after a patch produces a compliance incident. For Lyon, FR/EN bilingual delivery, B2B campaign calendars and French data-protection culture matter more than pretending to be Paris banking or Riviera tourism.
A short brief is enough to begin: which theme and plugins exist today, who edits (PL/FR/EN), when backups last restored successfully, whether the front is bilingual, where hosting sits and whether backups must stay in France, and whether Lyon IT requires Git and staging from day zero. WPPoland reviews the install, lists risks (unpatched Core, secrets in repo, broken FR/EN pair, consent plugin sending data outside the EU) and proposes a plan with acceptance criteria and SLA terms.
Contact: WPPoland contact form. The service pillar without city in the slug remains at WordPress maintenance. Custom development in Lyon is at WordPress developer in Lyon.
We serve clients in Lyon and nearby areas.
This page features specific insights for Lyon.
A WordPress site serving businesses in Lyon sits in Part-Dieu, in a Confluence office or in a Gerland laboratory. That proximity does not turn a marketing site into a congress booking platform for Centre de Congrès. It does mean updates, backups, consent plugins and form integrations are discussed before the first production change, not as an appendix after an incident that triggers a question from legal about GDPR and the Commission Nationale de l’Informatique et des Libertés (CNIL).
WPPoland delivers ongoing WordPress maintenance from a senior Polish team for businesses, laboratories and organisations with a base, branch or client base in Lyon and Métropole de Lyon. Scope is WordPress maintenance: tested updates, daily backups, security and performance monitoring, incident response under a written SLA, and up to four hours of small development changes per month. Custom theme builds and plugin development are separate topics, described on the WordPress developer in Lyon page.
Lyon is France’s second-largest economic centre after Paris: a chemical and pharmaceutical tradition, biotechnology in Gerland, logistics along the Rhône and a growing digital ecosystem around Confluence and Lyon Digital Hub. This is not Paris fintech or the Côte d’Azur tourist market. Here WordPress often serves B2B catalogues, employer-branding portals, laboratory enquiry forms or product pages for Part-Dieu firms that must survive a plugin update in the same week a lawyer asks about EU hosting and CNIL consent for cookies.
Part-Dieu is France’s second-largest business district after La Défense. Towers, Gare de Lyon-Part-Dieu, conference hotels and corporate offices create a context where WordPress holds product landings, demo forms, technical blogs and employer-branding pages. A plugin update breaking a form or an FR/EN translation regression hurts during a Part-Dieu congress week or before an investor meeting, not in August. Maintenance in Lyon must respect those windows, not treat every Tuesday as equal.
Confluence is the district south of Lyon, around Musée des Confluences and a newer startup ecosystem. Lyon Digital Hub and communities such as Silicon Rhône meet in this area. WordPress serves SaaS landings, beta registration forms, product blogs and FR/EN multilingual content for firms selling across the European Union. A maintenance brief from a client here often sounds like: “we have Elementor, editorial is scared of updates, and the CTO wants tested staging and Git”. That is an operations and process problem, not a marketplace template problem.
Gerland and the Lyonbiopôle biotechnology park are a different profile from a Part-Dieu corporation. More regulatory content, more PDF documents, more forms collecting personal data under GDPR and more audit-trail requirements. WordPress in this environment is a research portal, laboratory services catalogue or spin-off site that collects enquiries and must respect France’s Loi Informatique et Libertés and CNIL guidance. A consent log that disappears after a plugin update is a compliance incident, not a UX ticket.
The chemical and industrial sector in the Lyon metropolitan area generates another profile: parts catalogues, quotation request forms, distributor pages and FR/DE content for cross-border clients from Alsace or Switzerland. WordPress must survive a traffic spike after a new product line announcement, not just look good on a laptop in a Part-Dieu office.
The typical brief that reaches maintenance in Lyon does not read “keep it updated somehow”. It reads: last Core update was eight months ago, backup plugin shows green but nobody has restored since 2022, WPML or Polylang serving French text on the English version after a patch, and a new congress subpage broke because someone updated a page builder without staging. That is technical debt that surfaces on a Monday morning, not in an SEO audit.
WPPoland is not a contractor for Métropole de Lyon or a Part-Dieu tower management company. Proximity to France’s second business district sets the bar for documentation, roles and FR/EN bilingual delivery. It does not set a list of corporate references.
Maintenance in Lyon is a written SLA, not a vague “we look after the site”. The monthly package covers:
Pricing is individual and delivered in writing after scope is agreed. There is no rate card on this page.
Every engagement in Lyon starts with an onboarding audit, usually about one hour on the live install plus follow-up on staging setup. The audit documents:
| Area | What is checked |
|---|---|
| Plugin inventory | active plugins, last update dates, known CVEs, overlap with consent and cache layers |
| Hosting | PHP version, memory limits, object cache, TLS, CDN, EU residency if contract requires it |
| Backups | schedule, retention, last successful restore test, off-site copy |
| Security | admin accounts, 2FA, file permissions, XML-RPC, file editor, secrets in Git |
| FR/EN setup | WPML or Polylang configuration, hreflang, broken language pairs, string sync |
| Performance | Lighthouse baseline on homepage, CPT archive and a representative landing in both languages |
| Compliance hooks | consent plugin behaviour, form data flows, log retention, politique de confidentialité links |
Inherited installs are common. The first month often involves more remediation than routine maintenance: patching vulnerable plugins, fixing broken backups, removing malware, stabilising an FR/EN pair that drifted apart, or moving secrets out of wp-config.php in Git history. Remediation is listed with priorities before steady cadence begins. Steady maintenance does not start on a site where restore has never been verified.
The most expensive maintenance failure in Lyon is not a missed minor plugin update. It is a Core or major plugin update pushed to production on a Thursday because “it looked fine on localhost”, breaking the English version of a Part-Dieu product landing the day before a B2B campaign for the French and German markets.
Staging is a production copy with anonymised data. WP-CLI search-replace on URL, separate keys, crons that send mail to real addresses disabled. Editorial and IT click through staging with real Gutenberg patterns in both languages, not on the developer’s laptop. Multilingual regression, form submission, consent banner behaviour and keyboard navigation happen here.
Production promotion is a documented step: tag or merge, asset build, cache warmup, rollback path to the previous tag. The team does not “quick upload” one PHP file over SFTP, because nobody can reconstruct what was on production on Friday before a congress week in Part-Dieu.
Update cadence follows risk, not calendar superstition. Security patches for actively exploited CVEs move faster than cosmetic plugin updates. Major version jumps (PHP, Core, WooCommerce if present) get their own written plan and acceptance criteria. WooCommerce stores are a separate scope; if the brief includes checkout, see WooCommerce developer in Lyon.
Congress events in Part-Dieu, trade fairs at Eurexpo or product campaigns targeting the French and German markets create windows where hundreds of firms watch product landings, registration forms and CRM integrations. A site failure mid-congress week is not a “bug for the backlog”. It is lost leads and reputation damage with partners who have a full calendar for the quarter.
The maintenance runbook for clients in Lyon includes a production deploy freeze for campaign windows, usually from two weeks before an event until one week after. Critical security updates go through staging and a night window; everything else waits. That is not a developer preference. It is an operational decision agreed with the client before the season. Anyone doing a “small cache patch” on congress Monday learns when the site does not survive the traffic spike from attendees’ phones.
Hosting “in the EU” is a jurisdiction argument in procurement, not a magic shield. A form collecting personal data without legal basis is not fixed by a server in France alone. Maintenance still records where backups live, whether off-site copies cross borders, and what the client’s processor agreement requires.
Practical backup rules written into the runbook:
If the client requires backups to remain in France, that is a contract topic checked at onboarding against the actual provider configuration (OVH in France, Scaleway in Paris, AWS eu-west-3 in Paris, Claranet in Lyon), not an assumption from the TLD.
France applies GDPR alongside the national Loi Informatique et Libertés. The supervisory authority is the Commission Nationale de l’Informatique et des Libertés (CNIL). For WordPress maintenance in Lyon that is not an abstract legal paragraph. It is decisions in forms, consent plugins, politique de confidentialité and audit logs after every update cycle.
Posture maintainable in code and process:
What maintenance checks after updates that touch compliance:
CNIL publishes recommendations on cookies and tracking that affect GTM, Meta Pixel and similar tools. A consent plugin copied from a German shop is not automatically CNIL-aligned, and no banner is not automatically legal when tracking runs. WPPoland does not sell legal opinions. Maintenance ensures tools on the site match what stands in the politique de confidentialité, and that after a GTM or consent-plugin update consent logs still record correctly.
If a personal-data breach requires notification to CNIL, logs and the incident timeline must fit a notification workflow. WPPoland documents interventions with timeline, root cause and remediation steps. It does not file on behalf of the data controller.
The most common post-update regression in Lyon is not PHP fatal errors. It is the English version showing French strings because a plugin update reset language mappings or because someone edited the FR page and the EN copy was never synced.
Maintenance for bilingual sites in Lyon includes:
WPML and Polylang solve hreflang and language copies. They do not solve process: who approves French text, who approves English, before production. The maintenance runbook records whether approval sits with the client in Lyon, with the Polish content lead, or both in parallel.
Monitoring combines synthetic uptime checks, application-level alerts and security scanning. Alerts route to Slack and email with enough context to triage without logging into five dashboards.
Incident management follows ITIL-lite: detection, triage, resolution, post-mortem. Every confirmed incident gets a root cause summary within 48 hours. SLA compliance is tracked against the contracted uptime tier, with monthly reports surfacing target and actual rather than a marketing number.
Priority tickets: sub-four-hour response on weekdays. Confirmed security incidents and production outages: response outside hours where the SLA covers it. The intervention is logged with timeline, containment steps, remediation and follow-up risks. That log is what legal and IT in Lyon need when asking “what happened between 14:00 and 16:30 on Tuesday”.
Communication runs through a written ticketing channel. Calls unblock decisions; they do not replace the audit trail.
Speed in Lyon is not vanity. B2B firms and life-sciences organisations compete on credibility; a site that loads in four seconds on mobile loses form completions and signals neglect to reviewers accustomed to Part-Dieu project standards.
Performance maintenance includes:
Performance budgets are set at onboarding and checked against lab and, where available, CrUX field data. Regressions after updates are caught on staging, not discovered by the client on Monday morning before a seasonal campaign.
Maintenance is the steady state after launch, or the rescue lane for a site that outgrew DIY updates. If the site needs a new block theme, custom plugin or large refactor, scope moves to WordPress developer in Lyon. If the site needs checkout, Payplug integration or product catalogues, scope moves to WooCommerce developer in Lyon.
Development engagements end with a runbook: how to add a pattern, how to ship a branch, how to rebuild staging, whom to call when the editor will not save. Maintenance picks up that runbook and keeps it current as Core, plugins and hosting evolve. A handover without a runbook is a support ticket waiting to happen.
Lyon Digital Hub and communities such as Silicon Rhône are reference points for Lyon’s digital ecosystem: meetups, networking, projects linking administration, startups and IT suppliers in Confluence. They are not a WPPoland sales argument. They are a barometer: editorial and IT teams in Lyon ask about restore tests and staging because they heard those questions at local meetups and in corridors near Musée des Confluences.
The chemical and pharmaceutical tradition along the Rhône, plus Lyonbiopôle in Gerland, add reviewers who read monthly reports, not only marketing copy. A laboratory that loses CNIL consent logs after a patch produces a compliance incident. For Lyon, FR/EN bilingual delivery, B2B campaign calendars and French data-protection culture matter more than pretending to be Paris banking or Riviera tourism.
A short brief is enough to begin: which theme and plugins exist today, who edits (PL/FR/EN), when backups last restored successfully, whether the front is bilingual, where hosting sits and whether backups must stay in France, and whether Lyon IT requires Git and staging from day zero. WPPoland reviews the install, lists risks (unpatched Core, secrets in repo, broken FR/EN pair, consent plugin sending data outside the EU) and proposes a plan with acceptance criteria and SLA terms.
Contact: WPPoland contact form. The service pillar without city in the slug remains at WordPress maintenance. Custom development in Lyon is at WordPress developer in Lyon.
Explore selected projects supporting our clients' success.
scalac.io is an international platform founded in 2014 to meet the challenges associated with big data management and business operations scaling, specializing in Scala, distributed systems, and cryptography solutions.
Sprint.pl is a website created for Sprint S.A., an Olsztyn-based company operating since 1988 as a systems integrator and provider of advanced software. The ...
VECTOR Technologies is an international technology company specialising in the development and production of telecommunications systems for providers providers across Europe.
How we approach AI citations, WooCommerce B2B modernization, and NIS2-aligned operational resilience on WordPress. These guides apply to every client location.
Local expertise: - Senior WordPress maintenance for businesses in Lyon and Métropole de Lyon - Tested updates, daily backups with 30-day retention, malware scanning and WAF - Uptime and PageSpeed monitoring with documented SLA response times Our team understands the Lyon market and tailors solutions to local business needs. In practice, this means a focus on Core Web Vitals, local intent, and information architecture tailored to the Lyon market.
Let's discuss how we can bring top-tier performance to your project.
Schedule free consultation in LyonStay updated with the WordPress Maintenance & Support community
Since 26 August 2026, links in Google results go through google.com/goto instead of straight to the page. What this changes in analytics, in rank tracking tools and in WordPress, and what it does not change at all.
WP Rocket 3.23.2.1 and earlier fatal on WordPress 7.1: TypeError in Cloudflare.php line 562. GitHub report 6 July, sites down 19 August, fix 3.23.2.2 on 20 August. Update the plugin first.
Google now expands AI Overviews to a full AI Mode answer on some queries and pushes the ten blue links down. Our Search Console numbers on offer URLs at positions 2 to 4, and what we changed so the overview has a fact to cite.
Google changed its JSON-LD extraction and now applies only one pass of HTML unescaping. Double-escaped entities are no longer unrolled, so the block stops parsing and the structured data disappears. How to measure your own corpus and how to encode it correctly.
Google splits site reputation manual actions by searcher location from 30 August 2026. Outside the EEA the demotion still hits the affected portion. Inside the EEA that impact does not apply; the section may rank independently. Why parasite SEO does not return.
More articles are available on /en/blog/
The work comes mostly from Local SMB and Enterprise. The acceptance list for France runs through GDPR, NIS2 and EAA. None of that is specific to Lyon, it applies market-wide, but it is cheaper written into the scope than retrofitted after launch.
Yes. Communication runs through a written ticketing channel with monthly status reports. Calls are used only when needed to unblock decisions or walk through incident details. Lyon IT teams and compliance reviewers typically prefer English in the ticket trail and FR in editorial documentation.
Onboarding starts with a one-hour audit of your existing WordPress install: plugin inventory, hosting setup, backup state, security posture, FR/EN configuration, consent-plugin behaviour and a performance baseline. Findings are documented, monitoring and the first tested update cycle are set up, then the engagement moves to the steady monthly cadence with a written SLA.
Strengthen your business with professional technical support in key areas of the WordPress ecosystem.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Core Web Vitals, caching, and faster delivery.
Stability, updates, and post-launch support.
Migration to Astro, Next.js, and headless WordPress.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Audit, hardening, and incident risk reduction.
How to optimize Interaction to Next Paint (INP) on WordPress sites. Practical fixes for the newest Core Web Vital metric that directly impacts Google rankings.
Field versus lab, LCP, INP and CLS for WordPress in 2026. Google's green LCP is still 2.5 s in CrUX. 100/100 in Lighthouse is a lab target. Edge HTML, consent banners, checkout widgets.
Compare the best image optimisation plugins for WordPress, configure WebP/AVIF delivery, extract critical CSS, and set up LiteSpeed Cache for maximum PageSpeed scores.