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 corporate site in Lyon sits in Part-Dieu, in a Confluence office or in a Gerland laboratory. That is not a reason for WordPress to pretend it is an ERP system or a congress booking platform for Centre de Congrès. It is a reason for the theme, Gutenberg blocks, CPT and plugins to be written the way a French legal team, an FR/EN editor and a compliance team that reads GDPR and CNIL expect, not just the way a Lighthouse score expects.
WPPoland builds this WordPress from a senior Polish team for businesses in Lyon and Métropole de Lyon. Scope is WordPress development: block or classic theme, custom plugins, Gutenberg, CPT, ACF or native blocks, REST integrations and code review on Git. WooCommerce stores, maintenance retainers and contact are separate topics, with links at the end.
Lyon is France’s second-largest economic centre after Paris, a city with 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 deployment 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 for firms that just closed a funding round or prepare a B2B campaign for the French and German markets. 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.
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 brief from a client here often sounds like: “we have Elementor, editorial is scared of migration, and the CTO wants Gutenberg and Git”. That is a content-model and delivery-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.
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 project that reaches senior developers in Lyon does not sound like “make us a nice site”. It sounds like: inherited page-builder themes, a Gerland laboratory publishing a B2B offer in a narrow time window, a form with a SIRET field collecting personal data under GDPR and CNIL, and a new congress subpage built by copying last year’s page and manually swapping dates. That is technical debt that surfaces on a Monday morning, not in an SEO audit.
A new build in Lyon starts with a decision that costs months if you get it wrong: whether presentation lives in a block theme with theme.json, in classic PHP templates, and what goes into a plugin. That decision is written down before the first commit.
A block theme holds tokens: palette, typography scale, spacing, content widths. For a Part-Dieu firm that means a bold brand palette with WCAG 2.2 AA contrast preserved. For a Gerland laboratory it means a restrained layout, a readable typeface without ornament, and components that do not break on long chemical compound names or product codes. Block patterns describe repeatable layouts: hero with distributor map, team grid, operational notice block, laboratory offer card with date, footer with a politique de confidentialité link aligned with GDPR.
Full site editing (FSE) makes sense when the editorial team genuinely needs control over header and footer. In practice many B2B and life-sciences firms in Lyon do not want that: the header is a brand and compliance element, not a playground. The block theme stays, but template parts (header, footer) are locked, and editorial works within patterns and custom blocks.
Every custom block gets block.json, a category, an icon and attributes with schema. Where content must reach search engines and RSS, rendering goes server-side. React in the editor serves InspectorControls and preview, not a front-end SPA pretending to be WordPress. The handbook at developer.wordpress.org is the API contract source, not a training slide.
Inherited installations in Lyon are often five or seven years old: child theme on a commercial skeleton, ACF wired into page.php, shortcodes in content, jQuery from the pre-block era, a separate page copy for every Part-Dieu congress. Rewriting that to FSE “because it is 2026” costs more than fixing template hierarchy, extracting logic into a plugin, and adding Gutenberg only where editorial actually assembles new landings.
A classic theme stays when:
theme.json simplifies nothing;Even then new pieces go in as blocks, not as more shortcodes. A shortcode in 2019 content stays for migration. New code does not add more.
The boundary is simple and recorded in the runbook. The theme knows how to display. The plugin knows. B2B product CPT, CRM queue, REST endpoint for intranet, an “operational editor” role without publish_pages on the public production site: that is a plugin. Colours, grid, hero pattern: that is the theme. If the parts catalogue disappears after a theme change, the architecture was wrong.
A custom plugin has its own prefix, PSR-4 autoload, a main file with Plugin Name header and semver version, and tests where logic matters (congress dates, CRM field mapping, SIRET form validation). Business logic does not go into the theme’s functions.php, because functions.php dies with the theme, and a firm in Lyon changes branding partners more often than it changes its content model.
Layer comparison at kickoff:
| Layer | What lives there | Example in Lyon |
|---|---|---|
| Theme | presentation, tokens, patterns | Part-Dieu congress landing, footer with politique de confidentialité |
| Plugin | CPT, roles, REST, integrations | B2B product, laboratory offer, location, audit logs |
| Gutenberg | editorial without HTML | event pattern, location block, offer card |
| Staging and Git | process, not feature | branch, review, freeze before campaign |
Gutenberg without a content model ends with every subpage as a unique block collage and nobody able to produce a list. In Lyon lists are concrete: B2B products, laboratory offers, events, office locations (Part-Dieu is not Gerland, Gerland is not Confluence), publications, job openings. These are objects, not “another page in the tree”.
We register CPT with custom capabilities, not mapped to post. An operational editor edits a product card, not delete plugins. CPT archives get a template or query pattern. Single objects get a template that prevents layout drift beyond the agreed structure. Taxonomies stay separate: product type (industrial part, laboratory service, software) does not mix with blog tags.
ACF has a place here, but not as a block substitute. ACF fields on CPT work for data that is fields, not layout: congress date, season number, language version, catalogue PDF file, “embargo until” flag. Offer or article page layout is assembled in Gutenberg. Mixing ACF Flexible Content with the full block editor on the same object creates two sources of truth and an editor who does not know where to click.
Where ACF is unnecessary, block attributes in block.json are enough. A “location with map” block does not need a field group on every page. It needs attributes and possibly InnerBlocks for the description. Fewer plugins in the admin means less attack surface and fewer conflicts with consent and cache plugins.
A Part-Dieu congress landing copied from last year’s page is debt that surfaces on a Monday morning. A CPT object with season, date and material fields survives November 2027 without copying the tree. The template reads the object. The editor changes the date, not HTML.
A shortcode in content is debt visible only at migration. New code in Lyon goes in as a block with server render: semantic markup, attributes in the block comment, filterable output. A product-list block reads CPT, caches the query with a transient with explicit TTL and invalidation on save_post, not on every request during a seasonal campaign peak.
Block code review checks three things before a branch merges to main: whether the block works with JS disabled on the front preview, whether attributes have types and defaults, and whether it does not load the full editor build on the front. Gutenberg that adds a megabyte of React to a B2B catalogue page does not pass review.
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 a WordPress site in Lyon that is not an abstract legal paragraph. It is decisions in forms, consent plugins, politique de confidentialité and audit logs.
What we write into the brief and the code:
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. We do not sell legal opinions. We ensure 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.
For WooCommerce stores in EUR, payment gateway integration handling Stripe, Payplug, Mollie, TVA and invoices aligned with French tax law is a separate brief on the WooCommerce developer in Lyon page. This page stays with WordPress development, not checkout.
Personal data under GDPR raises the question: which jurisdiction hosts the server. OVH in France, Scaleway in Paris, AWS in Ireland (eu-west-1), Hetzner in Germany, Claranet in Lyon are different answers for a compliance officer, but all sit within the EU. Ashburn or Hillsboro is the United States and usually a veto without Standard Contractual Clauses or another transfer basis.
The question “is hosting in Lyon” comes up less often than “is it in the EU”. The operational answer is two-part. Jurisdiction: EU, data does not move overnight to a US bucket without agreement. Latency: origin in France or Ireland plus a CDN with TLS termination in the EU usually suffices for users in Lyon and central Europe. Residency decisions go into the runbook, not a slogan “hosting in Lyon”.
Multilingual FR/EN (sometimes FR/DE for Alsace or Swiss clients) requires a separate architectural decision. WPML for traditional WordPress or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. A French B2B form with a SIRET field and an English version without that field are not a 1:1 copy but two templates with different validation fields.
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 deployment 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.
B2B contact forms are the most common integration point for Part-Dieu firms and chemical producers. In practice that means connecting WordPress to CRM, field validation aligned with GDPR, and rate limiting on public endpoints so a form does not become a spam vector during a new offer announcement hour.
For Confluence firms the second recurring integration is SaaS product landings: demo system synchronisation, Vimeo or YouTube video embed, beta registration forms with CNIL-aligned fields. Every integration gets webhook documentation, an error matrix and end-to-end testing on staging before production deployment.
For Gerland laboratories the third integration is a research portal: publications, quotation request forms with data minimisation, document management system connection. Webhooks and form status must survive a plugin update. A laboratory that loses CNIL consent logs after a patch produces a compliance incident, not a UX ticket.
Every project in Lyon follows a structured process that minimises risk and maximises transparency:
Businesses in Lyon regularly come to us with these problems:
Core Web Vitals are a Google ranking factor and a conversion factor on a site collecting B2B leads during a seasonal campaign or congress week in Lyon. We do not promise a specific percentage delta before audit, because improvement scale depends on the starting state of each installation. What we do systematically:
Every performance decision is data-driven. We measure before and after, document impact and include a performance baseline in project documentation so regression after the next plugin update is visible immediately, not after the fact in a congress window.
A well-built site is valuable only when your target audience in Lyon and Métropole de Lyon can find it. Our WordPress development projects include foundational SEO architecture from the first sketch:
SEO is not a post-launch add-on. It is part of architectural decisions from the first sketch.
Can you migrate our existing site? Yes. We handle migrations from any CMS to WordPress, from WordPress to headless architecture (Astro/Next.js) and between hosting providers. Every migration includes URL mapping, 301 redirect implementation and SEO monitoring for 90 days after migration, with congress or seasonal campaign calendars considered so migration does not land in a critical window.
Do you work with firms outside Lyon? Yes. We know the local context (Part-Dieu, Confluence, Gerland, Lyon Digital Hub), but we work with clients across France and abroad. Many firms in Lyon serve clients in Paris, Alsace and across the European Union without a separate page for each city.
How do you handle multilingual sites? We implement multilingual setups through WPML for traditional WordPress or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. For firms serving the French and German markets, FR/EN/DE locale configuration requires a separate architectural decision.
What does ongoing support include? After build completion the project can move to dedicated WordPress maintenance in Lyon: tested updates, backups, security and performance monitoring, and priority support with a documented runbook. Details are on the maintenance page, not in this development brief.
How does working with WPPoland differ from a local agency in Lyon? Primarily WordPress experience since 2007, our own technical stack on Astro and headless WordPress, and work on clear assumptions: scope, stages and responsibility are described before deployment. Pricing is individual and depends on scope, not a fixed price list.
If your firm already runs an online store or plans to build one, we have a dedicated page on WooCommerce developer in Lyon with French checkout, Payplug integration and GDPR with CNIL preparation. If the current site works and needs only ongoing care, tested updates and monitoring, see WordPress maintenance in Lyon. Both describe the same technical stack from an operational perspective, not a development one.
The full scope of WordPress development work (themes, plugins, Gutenberg, refactors) is described on the WordPress developer pillar. To discuss a brief, send a short description of your current situation through the contact form.
If you want to discuss WordPress development, send a short description of your current situation, business goal and technical constraints. From that we review the configuration, identify risks and propose a practical action plan.
If you are planning a new build, Gutenberg migration or refactor of an inherited theme before a Part-Dieu congress or Confluence campaign, start by writing down goals, constraints and current project state. Pricing is individual and depends on the scope of work.
We serve clients in Lyon and nearby areas.
This page features specific insights for Lyon.
A corporate site in Lyon sits in Part-Dieu, in a Confluence office or in a Gerland laboratory. That is not a reason for WordPress to pretend it is an ERP system or a congress booking platform for Centre de Congrès. It is a reason for the theme, Gutenberg blocks, CPT and plugins to be written the way a French legal team, an FR/EN editor and a compliance team that reads GDPR and CNIL expect, not just the way a Lighthouse score expects.
WPPoland builds this WordPress from a senior Polish team for businesses in Lyon and Métropole de Lyon. Scope is WordPress development: block or classic theme, custom plugins, Gutenberg, CPT, ACF or native blocks, REST integrations and code review on Git. WooCommerce stores, maintenance retainers and contact are separate topics, with links at the end.
Lyon is France’s second-largest economic centre after Paris, a city with 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 deployment 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 for firms that just closed a funding round or prepare a B2B campaign for the French and German markets. 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.
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 brief from a client here often sounds like: “we have Elementor, editorial is scared of migration, and the CTO wants Gutenberg and Git”. That is a content-model and delivery-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.
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 project that reaches senior developers in Lyon does not sound like “make us a nice site”. It sounds like: inherited page-builder themes, a Gerland laboratory publishing a B2B offer in a narrow time window, a form with a SIRET field collecting personal data under GDPR and CNIL, and a new congress subpage built by copying last year’s page and manually swapping dates. That is technical debt that surfaces on a Monday morning, not in an SEO audit.
A new build in Lyon starts with a decision that costs months if you get it wrong: whether presentation lives in a block theme with theme.json, in classic PHP templates, and what goes into a plugin. That decision is written down before the first commit.
A block theme holds tokens: palette, typography scale, spacing, content widths. For a Part-Dieu firm that means a bold brand palette with WCAG 2.2 AA contrast preserved. For a Gerland laboratory it means a restrained layout, a readable typeface without ornament, and components that do not break on long chemical compound names or product codes. Block patterns describe repeatable layouts: hero with distributor map, team grid, operational notice block, laboratory offer card with date, footer with a politique de confidentialité link aligned with GDPR.
Full site editing (FSE) makes sense when the editorial team genuinely needs control over header and footer. In practice many B2B and life-sciences firms in Lyon do not want that: the header is a brand and compliance element, not a playground. The block theme stays, but template parts (header, footer) are locked, and editorial works within patterns and custom blocks.
Every custom block gets block.json, a category, an icon and attributes with schema. Where content must reach search engines and RSS, rendering goes server-side. React in the editor serves InspectorControls and preview, not a front-end SPA pretending to be WordPress. The handbook at developer.wordpress.org is the API contract source, not a training slide.
Inherited installations in Lyon are often five or seven years old: child theme on a commercial skeleton, ACF wired into page.php, shortcodes in content, jQuery from the pre-block era, a separate page copy for every Part-Dieu congress. Rewriting that to FSE “because it is 2026” costs more than fixing template hierarchy, extracting logic into a plugin, and adding Gutenberg only where editorial actually assembles new landings.
A classic theme stays when:
theme.json simplifies nothing;Even then new pieces go in as blocks, not as more shortcodes. A shortcode in 2019 content stays for migration. New code does not add more.
The boundary is simple and recorded in the runbook. The theme knows how to display. The plugin knows. B2B product CPT, CRM queue, REST endpoint for intranet, an “operational editor” role without publish_pages on the public production site: that is a plugin. Colours, grid, hero pattern: that is the theme. If the parts catalogue disappears after a theme change, the architecture was wrong.
A custom plugin has its own prefix, PSR-4 autoload, a main file with Plugin Name header and semver version, and tests where logic matters (congress dates, CRM field mapping, SIRET form validation). Business logic does not go into the theme’s functions.php, because functions.php dies with the theme, and a firm in Lyon changes branding partners more often than it changes its content model.
Layer comparison at kickoff:
| Layer | What lives there | Example in Lyon |
|---|---|---|
| Theme | presentation, tokens, patterns | Part-Dieu congress landing, footer with politique de confidentialité |
| Plugin | CPT, roles, REST, integrations | B2B product, laboratory offer, location, audit logs |
| Gutenberg | editorial without HTML | event pattern, location block, offer card |
| Staging and Git | process, not feature | branch, review, freeze before campaign |
Gutenberg without a content model ends with every subpage as a unique block collage and nobody able to produce a list. In Lyon lists are concrete: B2B products, laboratory offers, events, office locations (Part-Dieu is not Gerland, Gerland is not Confluence), publications, job openings. These are objects, not “another page in the tree”.
We register CPT with custom capabilities, not mapped to post. An operational editor edits a product card, not delete plugins. CPT archives get a template or query pattern. Single objects get a template that prevents layout drift beyond the agreed structure. Taxonomies stay separate: product type (industrial part, laboratory service, software) does not mix with blog tags.
ACF has a place here, but not as a block substitute. ACF fields on CPT work for data that is fields, not layout: congress date, season number, language version, catalogue PDF file, “embargo until” flag. Offer or article page layout is assembled in Gutenberg. Mixing ACF Flexible Content with the full block editor on the same object creates two sources of truth and an editor who does not know where to click.
Where ACF is unnecessary, block attributes in block.json are enough. A “location with map” block does not need a field group on every page. It needs attributes and possibly InnerBlocks for the description. Fewer plugins in the admin means less attack surface and fewer conflicts with consent and cache plugins.
A Part-Dieu congress landing copied from last year’s page is debt that surfaces on a Monday morning. A CPT object with season, date and material fields survives November 2027 without copying the tree. The template reads the object. The editor changes the date, not HTML.
A shortcode in content is debt visible only at migration. New code in Lyon goes in as a block with server render: semantic markup, attributes in the block comment, filterable output. A product-list block reads CPT, caches the query with a transient with explicit TTL and invalidation on save_post, not on every request during a seasonal campaign peak.
Block code review checks three things before a branch merges to main: whether the block works with JS disabled on the front preview, whether attributes have types and defaults, and whether it does not load the full editor build on the front. Gutenberg that adds a megabyte of React to a B2B catalogue page does not pass review.
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 a WordPress site in Lyon that is not an abstract legal paragraph. It is decisions in forms, consent plugins, politique de confidentialité and audit logs.
What we write into the brief and the code:
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. We do not sell legal opinions. We ensure 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.
For WooCommerce stores in EUR, payment gateway integration handling Stripe, Payplug, Mollie, TVA and invoices aligned with French tax law is a separate brief on the WooCommerce developer in Lyon page. This page stays with WordPress development, not checkout.
Personal data under GDPR raises the question: which jurisdiction hosts the server. OVH in France, Scaleway in Paris, AWS in Ireland (eu-west-1), Hetzner in Germany, Claranet in Lyon are different answers for a compliance officer, but all sit within the EU. Ashburn or Hillsboro is the United States and usually a veto without Standard Contractual Clauses or another transfer basis.
The question “is hosting in Lyon” comes up less often than “is it in the EU”. The operational answer is two-part. Jurisdiction: EU, data does not move overnight to a US bucket without agreement. Latency: origin in France or Ireland plus a CDN with TLS termination in the EU usually suffices for users in Lyon and central Europe. Residency decisions go into the runbook, not a slogan “hosting in Lyon”.
Multilingual FR/EN (sometimes FR/DE for Alsace or Swiss clients) requires a separate architectural decision. WPML for traditional WordPress or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. A French B2B form with a SIRET field and an English version without that field are not a 1:1 copy but two templates with different validation fields.
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 deployment 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.
B2B contact forms are the most common integration point for Part-Dieu firms and chemical producers. In practice that means connecting WordPress to CRM, field validation aligned with GDPR, and rate limiting on public endpoints so a form does not become a spam vector during a new offer announcement hour.
For Confluence firms the second recurring integration is SaaS product landings: demo system synchronisation, Vimeo or YouTube video embed, beta registration forms with CNIL-aligned fields. Every integration gets webhook documentation, an error matrix and end-to-end testing on staging before production deployment.
For Gerland laboratories the third integration is a research portal: publications, quotation request forms with data minimisation, document management system connection. Webhooks and form status must survive a plugin update. A laboratory that loses CNIL consent logs after a patch produces a compliance incident, not a UX ticket.
Every project in Lyon follows a structured process that minimises risk and maximises transparency:
Businesses in Lyon regularly come to us with these problems:
Core Web Vitals are a Google ranking factor and a conversion factor on a site collecting B2B leads during a seasonal campaign or congress week in Lyon. We do not promise a specific percentage delta before audit, because improvement scale depends on the starting state of each installation. What we do systematically:
Every performance decision is data-driven. We measure before and after, document impact and include a performance baseline in project documentation so regression after the next plugin update is visible immediately, not after the fact in a congress window.
A well-built site is valuable only when your target audience in Lyon and Métropole de Lyon can find it. Our WordPress development projects include foundational SEO architecture from the first sketch:
SEO is not a post-launch add-on. It is part of architectural decisions from the first sketch.
Can you migrate our existing site? Yes. We handle migrations from any CMS to WordPress, from WordPress to headless architecture (Astro/Next.js) and between hosting providers. Every migration includes URL mapping, 301 redirect implementation and SEO monitoring for 90 days after migration, with congress or seasonal campaign calendars considered so migration does not land in a critical window.
Do you work with firms outside Lyon? Yes. We know the local context (Part-Dieu, Confluence, Gerland, Lyon Digital Hub), but we work with clients across France and abroad. Many firms in Lyon serve clients in Paris, Alsace and across the European Union without a separate page for each city.
How do you handle multilingual sites? We implement multilingual setups through WPML for traditional WordPress or native i18n routing for headless builds with Astro or Next.js. Each language version gets correct hreflang tags, localised URL slugs and independent SEO meta data. For firms serving the French and German markets, FR/EN/DE locale configuration requires a separate architectural decision.
What does ongoing support include? After build completion the project can move to dedicated WordPress maintenance in Lyon: tested updates, backups, security and performance monitoring, and priority support with a documented runbook. Details are on the maintenance page, not in this development brief.
How does working with WPPoland differ from a local agency in Lyon? Primarily WordPress experience since 2007, our own technical stack on Astro and headless WordPress, and work on clear assumptions: scope, stages and responsibility are described before deployment. Pricing is individual and depends on scope, not a fixed price list.
If your firm already runs an online store or plans to build one, we have a dedicated page on WooCommerce developer in Lyon with French checkout, Payplug integration and GDPR with CNIL preparation. If the current site works and needs only ongoing care, tested updates and monitoring, see WordPress maintenance in Lyon. Both describe the same technical stack from an operational perspective, not a development one.
The full scope of WordPress development work (themes, plugins, Gutenberg, refactors) is described on the WordPress developer pillar. To discuss a brief, send a short description of your current situation through the contact form.
If you want to discuss WordPress development, send a short description of your current situation, business goal and technical constraints. From that we review the configuration, identify risks and propose a practical action plan.
If you are planning a new build, Gutenberg migration or refactor of an inherited theme before a Part-Dieu congress or Confluence campaign, start by writing down goals, constraints and current project state. Pricing is individual and depends on the scope of work.
Explore selected projects supporting our clients' success.
AirHelp was founded in 2013 as a start-up and has grown to become the global leader in defending air passenger rights, helping over 13 million people underst...
alextg.pl is a WordPress website for a company that helps customers obtain financing. The project focused on clear service presentation, contact flow and stable technical upkeep...
The andergrant.com project was created in 2009 as a website for the largest club in Olsztyn, utilizing project-specific technical choices of that era including PHP 5, MySQL, jQuery, and Flash multimedia.
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 development for businesses in Lyon: custom themes, Gutenberg block patterns, CPT, ACF or native block attributes, and custom plugins - Local context: Part-Dieu, Confluence, Lyon Digital Hub, Gerland biotech, Rhône-Alpes chemical sector and Métropole de Lyon - WordPress Coding Standards, GDPR with French CNIL, EU hosting and FR/EN versions built into the delivery process, without claiming a certification we did not earn 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 Developer 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.
Both. A new project in Lyon usually starts with a block theme built on editor APIs: theme.json, block patterns, variations. Inherited installations from Part-Dieu firms or Gerland laboratories more often need a focused refactor of template hierarchy and asset pipeline than a full rewrite. The decision is made on cost-versus-debt grounds, not on what is more interesting to build.
For new builds the default is a block theme with full site editing, because that is where the WordPress editor is going. Classic PHP themes remain when existing template logic is too expensive to port, or when the editorial team works in the classic editor and a tool change would be a bigger risk than technical debt. The choice is documented as a written trade-off, not an ideological decision.
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.