{"id":6969,"date":"2026-06-17T15:42:42","date_gmt":"2026-06-17T13:42:42","guid":{"rendered":"https:\/\/arkone.fr\/2026\/06\/17\/ai-and-the-web-what-really-changes-and-what-doesnt\/"},"modified":"2026-06-17T15:46:43","modified_gmt":"2026-06-17T13:46:43","slug":"ai-and-the-web-what-really-changes-and-what-doesnt","status":"publish","type":"post","link":"https:\/\/arkone.fr\/en\/2026\/06\/17\/ai-and-the-web-what-really-changes-and-what-doesnt\/","title":{"rendered":"AI and the web: what really changes (and what doesn’t)"},"content":{"rendered":"
\n
\n
\n
\n

Will artificial intelligence<\/strong> replace developers<\/strong> ? Kill WordPress<\/strong> ? Standardize the web<\/strong> to the point of draining it of its substance? We hear all sorts of conflicting opinions. <\/p>\n

To separate fact from fiction<\/strong> , the Yucatan<\/a> agency's Rencontres<\/em><\/strong><\/a> podcast brought together the two co-founders of Arkone<\/strong> , a Parisian web and mobile agency, for a frank conversation about what AI is transforming \u2014 or not \u2014 in the design, development and visibility of websites.<\/p>\n<\/div>\n<\/div><\/div>\n\n

\"Podcast<\/span><\/a><\/div>\n\n
\n

Arkone, putting people first<\/h2>\n

Before getting to the heart of the matter, a word about the agency. Arkone<\/strong> is a small, four-person team that prides itself on a deeply human approach. Almost everything is developed in-house, and each client receives comprehensive support from start to finish: from initial specifications to hosting, including development, SEO, and maintenance. <\/p>\n

The agency also makes a strong commitment: 100% French<\/strong> . Developers, designers, freelancers\u2014all are recruited in France, both for the quality of their work and to ensure seamless communication, eliminating information loss due to language barriers. And contrary to popular belief, showcase websites represent only a tiny fraction of their business: Arkone<\/a> focuses primarily on mobile and business applications, with careful consideration of client needs from the outset. <\/p>\n<\/div>\n<\/div><\/div>\n\n

\"Co-founders<\/span><\/div>\n\n
\n

From developer to project manager<\/h2>\n

S\u00e9bastien and Valentin's observation is unequivocal: since September 2023, the job has completely changed. It has gone from a highly technical task\u2014writing the code yourself\u2014to a role more akin to that of a project manager leading an AI. <\/p>\n

But be warned: this doesn't mean the profession has become less demanding; quite the opposite. The focus has shifted upstream. Preparing the code structure, writing the right prompt based on the client's request, knowing how to precisely articulate what you want: these are the new key skills. As S\u00e9bastien, an AI, aptly summarizes, \"You have to talk to it a bit like you would to a five-year-old.\" You can't just say, \"You know what I mean.\" <\/p>\n

\n

Technical control remains essential to verify the quality of the product code.\n<\/p>\n<\/p><\/div>\n<\/div>\n<\/div><\/div>\n\n

\n

\"Develop me a website\": the limits of magic<\/h2>\n

Can we really ask an AI to create a website from scratch? Yes\u2026 in theory. But the results need to be qualified. Arkone regularly takes over projects \u201cin the second phase\u201d: clients who had launched a website themselves with AI, which worked very well, until the day everything started malfunctioning without any apparent explanation. <\/p>\n

The problem? Code that is often unreadable and impossible to maintain. S\u00e9bastien compares AI to a junior developer just starting out: without a structure imposed from the outset, it produces \"unmanageable\" code that ultimately leads the project to disaster. AI can create good prototypes, but without a solid development foundation, the result doesn't hold up over time. <\/p>\n<\/div>\n<\/div><\/div>\n\n

\n

The end of WordPress?<\/h2>\n

For fifteen years, WordPress reigned supreme among CMSs. Today, its future is more uncertain. The famous CMS offered ease of use, but also its share of constraints: it was impossible to develop custom features without using plugins, which quickly became very complicated. <\/p>\n

However, AI now offers the same speed as WordPress, without the constraints, and with the quality of customization. According to the two founders, traditional templates are \"somewhat obsolete\" in the face of this new flexibility. WordPress isn't destined to disappear, but it has good reason to be concerned about a portion of its market. <\/p>\n<\/div>\n<\/div><\/div>\n\n

\"Developers<\/span><\/div>\n\n
\n

SEO, GEO: Visibility is changing the rules<\/h2>\n

A beautiful website that no one can find is useless. And here too, the rules are evolving rapidly. We've been talking about SEO<\/strong> for years; now we talk about GEO<\/strong> (Generative Engine Optimization), optimization for generative search engines. <\/p>\n

The difference is significant. Traditional SEO relied on a highly technical approach: tags, meta descriptions, and keywords placed in the right places. Search engines based on LLM (Learning Link Management), however, expect something else: context<\/strong> , expertise<\/strong> , in-depth content, and consistency across the entire site. Gone are the days of generic pages crammed with keywords. Instead, focus on precise answers, FAQs that provide context, and cited sources. <\/p>\n

One image keeps recurring in the conversation: websites now need to be built as if they were designed for a visually impaired person<\/strong> . Users with low mental health (LMH) read the site much like a screen reader. Structure, readability, tags, and metadata therefore remain essential\u2014even if their relative importance has decreased. <\/p>\n

And what about SEO in all of this? It's not dead, far from it. The two approaches complement each other and, on the positive side, they both encourage websites to be more accessible. <\/p>\n<\/div>\n<\/div><\/div>\n\n

\n

Accessibility, the quiet winner<\/h2>\n

This is one of the most beneficial side effects of this evolution. Accessibility is almost never spontaneously requested by customers\u2014the market isn't mature enough yet. But search engine optimization, whether SEO or GEO, forces<\/strong> websites to be accessible: contrasts checked, texts readable, nothing hidden. <\/p>\n

For Valentin, this isn't an abstract concept: Arkone has a visually impaired client, and the team sees firsthand how a well-designed website impacts their access to information. Therefore, the need for businesses to be visible on AI platforms indirectly benefits all users. <\/p>\n

Mobile first\u2026 or not<\/h2>\n

Should we always think \"mobile first\"? Not necessarily, says Arkone, which rejects dogma. It all depends on the sector and the actual use case. <\/p>\n

For business platforms, data-rich intranets, or competitive intelligence tools, usage is almost exclusively on desktop computers\u2014responsive design is sometimes completely irrelevant. Conversely, as soon as we enter the B2C market, mobile dominates: 60 to 70% of traffic, or even 80% for a restaurant website. This makes sense: people search for a restaurant on the go, or while relaxing on their sofa, rarely at their desk. In this case, mobile-first is always the order of the day. <\/p>\n

On the AI \u200b\u200bside, the picture is mixed: it's quite good at producing visually appealing responsive designs, but less adept at structuring, optimizing loading speed, and maintaining clean code. This is where choosing the right technologies\u2014for example, server-side rendering to deliver pre-built HTML and accelerate loading\u2014makes all the difference. And these fundamental decisions are ones that AI cannot make on its own. <\/p>\n<\/div>\n<\/div><\/div>\n\n

\"Presentation<\/span><\/div>\n\n
\n

Several AIs are better than one<\/h2>\n

Another lesson from this episode: to work effectively, you need to combine AI tools<\/strong> . Each one has its strengths, each shines at a particular time, and one can even be used to structure a prompt intended for another. The recipe? Constant curiosity, a lot of monitoring, and a great deal of testing, because the ranking of the best tools is constantly changing. <\/p>\n

Do we still need to learn to code?<\/h2>\n

Without hesitation: yes. Engineering schools aren't going anywhere. At Arkone, interns are even forbidden from using AI<\/strong> : they must first get their hands dirty, face the challenges, and understand the code. It's this experience that will later allow them to make the right strategic decisions\u2014server or client, type of hosting, etc. Without this knowledge, you can't guide the AI, which will systematically take the fastest route, which is rarely the best for a given project. <\/p>\n

Does AI pose a risk to the web?<\/h2>\n

That's the big question at the end. And the answer worries the two founders a little. <\/p>\n

The first risk, already visible, is the industrialization of the web<\/strong> : a multitude of sites that all look alike, with a recognizable graphic and textual \"style,\" and empty content because it's already been seen everywhere. AI doesn't create information, it recycles it. Many users don't even proofread their own posts. <\/p>\n

The second risk is even more profound: that of AI self-sabotage<\/strong> . If future models are trained on data themselves generated by AI, we risk widespread repetition, a \"monothink,\" a standardization of everything. A precedent already exists: the generated images had at one point all turned a yellowish tint, a sign of training on previous AI output. With text, the phenomenon would be more difficult to detect. <\/p>\n

Faced with this, two scenarios for the web of tomorrow: on the one hand a generic and standardized web, on the other a more artisanal<\/strong> , deeper, more human web.<\/p>\n<\/div>\n<\/div><\/div>\n\n

\n

Conclusion: The human element as a differentiating factor<\/h2>\n

This is where Arkone<\/a> 's true added value lies. Beyond the technical aspects, the agency's role is to remind the client that it's their<\/strong> expertise, their<\/strong> voice, that must be heard. AI can be used, but the human element must be maintained. <\/p>\n

This exchange\u2014questioning specifications, encouraging reflection, reworking texts to truly align with the client's objectives\u2014will remain, according to S\u00e9bastien and Valentin, the differentiating factor that will ensure the agency's longevity. The conclusion can be summed up in a simple sentence: we need to communicate.<\/strong> <\/p>\n

Find the full conversation in the episode of the podcast Rencontres<\/strong><\/a> , the podcast from the Yucatan<\/a> agency.<\/em><\/p>\n