Editorial policy

Who writes

Content is published by WebConsulting, a sole proprietorship founded by Benjamin M. No article is sponsored and no link is an affiliate link: when I mention a tool or a provider, I am not paid to do so. See the founder page.

How I source

• An external figure comes with a link to its primary source: report, study or official documentation.
• A figure that cannot be tied to a verifiable source is removed or replaced.
• Statements about how I work are labelled "WebConsulting method", so they are not mistaken for external data.
• Measurements of my own sites are dated and repeatable: the commands used are published on the Sources page.

See the Sources and method page.

How I review

Before publication, figures are checked against their source, links are opened and the text is read in full. Pages show their update date. This check is not infallible: the log below shows errors that got through, and how they were corrected.

How I use AI

A traditional agency means salaried staff, offices and equipment to pay off, and those fixed costs end up in its prices. WebConsulting made a different choice: artificial intelligence tools act as a team of assistants. They prepare drafts, suggest structures, review code, look for sources and spot inconsistencies.

What is not spent on salaries, offices and equipment goes to two things: more time on the quality of each project, and lower prices.

What AI does not do: decide, publish or answer you. Every piece of content is reviewed and approved by Benjamin M. before going live, and he answers for it. You always talk to a human.

Report an error

A doubtful figure, a source you cannot find, a dead link: write to me with the page address. Reply within 48 business hours. If the error is confirmed, the page is corrected and the correction added to the log below, with its date. contact@web-consulting.fr

Corrections log

Substantive corrections, most recent first. Typos and rewordings that do not change the meaning are not listed.

1. September 27, 2026. Pages: Portfolio (5 emergency demos).

   Descriptions of the plumber, locksmith, electrician, heating and glazier demos checked against the live sites. Corrected: "service-area pages" (it is a section of the homepage), "Qualifelec certifications" (absent from the electrician demo), "direct call button" and "phone number in sticky header" for the electrician and glazier demos (their buttons lead to the quote form).

2. September 27, 2026. Pages: Astro website creation, WordPress or Astro guide.

   English, Spanish and Guarani versions: statements of my own, on static-site security and the performance gap between Astro and WordPress, were presented as coming from HTTP Archive's Web Almanac. They are my own method: they are now labelled "WebConsulting method", and the guide's unsourced Lighthouse averages were removed, as in the French version.

3. September 27, 2026. Pages: AI visibility (GEO).

   "A page ranked #1 on Google has a ~58% chance of being cited by ChatGPT (AirOps, 354,000 pages)" misread the study: the ranking measured is within the results ChatGPT retrieves, not Google's. Corrected to: a page ranked 1st in those results is cited 58% of the time, versus 14% at 10th (AirOps, 353,799 pages, 2026), with a link to the study.

4. September 27, 2026. Pages: Astro website creation, Website maintenance, WordPress or Astro guide.

   On the Astro creation and Maintenance pages and in the guide, two WordPress security figures were cited without a link: "90% of CMS attacks" targeting WordPress (attributed to Sucuri) and "97% of vulnerabilities" coming from plugins (attributed to WPScan or Patchstack depending on the page). Replaced with more recent, verified and linked figures: WordPress accounted for 95.5% of infected sites cleaned by Sucuri in 2023, and of 11,334 WordPress vulnerabilities found in 2025, 91% were in plugins, 9% in themes and 6 in core (Patchstack).