Skip to content

NVIDIA Member of the NVIDIA Inception program

Webfluence

All articlesWebsites

What we check before a site goes live

Anyone can generate a website. Securing it is a job: someone on our team reviews everything before every launch.

FrédéricNovember 12, 20268 min

The key points

  • A site that looks fine isn't necessarily ready. Every launch is reviewed and approved by someone on our team.
  • The review covers your forms and payments, your customers' data, hosting, your visitors' comfort, Google and AI tools, then the law.
  • Five checks you can do yourself, no technical knowledge needed. You can run them on your site today.

Summarize withChatGPTClaudePerplexity

Anyone can generate a website. A tool builds you one in a few minutes, and it looks finished. That's exactly the trap: what matters most doesn't show on the screen.

A form can send nothing. A page can stay invisible to Google. A personal phone number can sit in the code. None of that jumps out at you on launch day.

So every launch is reviewed and approved by someone on our team.

A person reviews, and a person approves

A tool can catch an oversight. It can't tell you whether your quote request lands in the right inbox, or whether your contact page reassures a customer. So a person decides whether your site can go live. Here, that person has a name: Frédéric, a software engineer for 30 years.

The review, in order

  1. Forms and payments

    Every request lands in the right place, and the data sent stays protected.

  2. Your customers' data

    It is encrypted, and only the right people can get to it.

  3. Hosting and updates

    The site sits on a healthy base, kept up to date and monitored.

  4. Your visitors' comfort

    The site loads fast and reads well on a phone.

  5. Google and AI tools

    Your pages can be read and understood.

  6. The law

    The required notices are there and up to date.

Your forms and payments

Your contact form is your front desk. If it quietly breaks, you lose customers without knowing it. So we send real test requests and check that they arrive in the right place, in full.

A form is also an open door to your site. Poorly protected, it gets flooded with junk messages, or it gets used to send them in your name. It has to let your customers through and stop the rest.

On an online store, payment goes through a specialized service. Your customers' card numbers have no business staying on your site. We check that path from end to end, from the cart to the order confirmation.

Your customers' data

A name, an email address, a phone number: as soon as your site receives them, you have to look after them.

The first layer of protection is an encrypted connection: the https at the start of the address. What a visitor sends can't be read along the way. Browsers don't always show that https anymore, or the small padlock. Without encryption, though, they warn your customer with a Not secure alert.

We also check what you can't see: who can access the data, where it's stored, and what the code of your pages lets people read. Information hidden on the screen is still public if it sits in the code. A personal phone number can stay readable by any bot, even though it doesn't appear anywhere on the page.

A public page includes everything that can be read in its code.

Hosting, updates, monitoring

Once it's live, a site runs on a server, and its parts age.

Hosting is the place where your site is stored so it stays available. Updates fix known security holes. Monitoring alerts us when something goes wrong, before your customers tell you.

Before launch, we make sure each of these three has an owner. Your domain name is your address on the internet: we check whose name it's registered in, and who handles what on the day there's a problem.

Your visitors' comfort

A site can be very well protected and still drive people away. So we put ourselves in their place.

2.5 seconds

to display the main content: the threshold Google calls good.

That benchmark comes from Google. To hit it, we start with image weight. We also check that the page doesn't jump while it loads, when a button moves just as you're about to tap it.

On phones, we test each page template at 360 pixels wide, a small screen, and nothing can overflow. Buttons and links are at least 44 pixels, a comfortable size for a finger. Text stays readable against its background, including for people with poor eyesight.

The width of our phone tests

Your pages, as Google and AI tools see them

A site can be beautiful and stay invisible. During construction, we often ask Google not to show it, so an unfinished version doesn't appear in its results. If that instruction stays in place on launch day, your site doesn't appear. It's a one-line oversight, and an expensive one.

We check that every page has a unique title, that Google has the site map, and that old addresses lead to the new ones.

We also look at AI bots. If overly strict security settings block them, your pages can't be read, or cited in their answers. See what Google and AI read on your site.

In France, a business website has to say who publishes it. That's the legal notice. It includes your company name, contact details, registration, your host's name and contact details, and the publication director, the person responsible for the content.

If your site collects data, a privacy policy explains what you do with it. If it sets cookies that track your visitors, they have to be able to refuse them as easily as they accept them. An online store also needs its terms of sale.

Some professions, like insurance or financial advice, have extra notices. We identify them with you before launch.

Nothing goes liveuntil a person has reviewed it

After launch

The review doesn't stop on launch day. You add pages, tools change, new security holes turn up. A site that's up to date today won't stay that way on its own.

That's why we stick around afterward. Hosting, updates, monitoring: that quiet work saves you from nasty surprises.

Five checks you can run yourself

You don't need to be technical. Grab your phone and try these on your site.

Five tests, on your site

The testHow to do itWhat it tells you
The connectionMake sure no Not secure warning shows in the address barIf the warning shows, your connection isn't encrypted. Fix this first
The phoneOpen your site on your phone and go through every pageIf you have to zoom or swipe sideways, so do your visitors
The formSend yourself a real requestIf nothing arrives, your customers' requests don't either
GoogleType site:yoursite.com into GoogleIf nothing appears, your site is invisible on Google. A setting may be blocking it
The footerLook for the legal notice and the privacy policyIf one is missing, add it

To go further, enter your website address in our free analysis: in a few minutes, you get a first look at its speed, its search rankings and its security.

Planning a new site? See what we offer for websites. You'll know who reviewed it before it goes live.

Frédéric

Head of information systems

Frédéric runs hosting, maintenance and security for everything we put online. 30 years of software engineering.

Questions we get on this topic

  • Not necessarily. The risk comes from skipping the review. Have someone check what's behind the screen before customers start using it and sharing their data.

  • Not on its own. It's essential, but it says nothing about your forms, your updates or your access.

  • Yes. Start with the free analysis. To go further, our full audit is a paid service: a person goes through your site page by page and tells you what to fix, in the right order.

Read next to go further