EO analysis of Winicar by Grégoire Vigneron

[mdsojolh444]

First SEO note on authority/difficulty

Old, ultra-competitive, very mature sector.

Very difficult for a new entrant to become “authoritative” on keywords related to the activity.
Competitors have a very large volume of external links (> 400,000 links for lacentrale.fr). There is therefore a long linking work to be done.
The age and size of the sites are also important elements of authority, which will take time to work on (size of the catalog, etc.)
Probably a strong dependence on SEA in the medium term (years) with large budgets and high CPC
To put it bluntly: you are tackling one of the most difficult areas in SEO…

However, this does not prevent us from improving certain on-site points.

User experience

Engines favor sites that provide a good user experience.

Loading time

Loading time is an important quality signal, which chinese overseas canada database therefore influences SEO
The home page is 2.5MB. That's way too much.
The weight of images in the result lists can be reduced by at least 60% without loss of quality. And by 80% on the home page.
The server side response time is very long (900ms on average on the lists)
New window

Opening a new tab when clicking on a link is considered a negative element in the user experience. It is a bad signal for SEO.
Navigation / Internal layout

The main search engine criteria should be navigable (not just rendered via js).
In particular, one should be able to navigate the lists by brand (only accessible from the footer) and model.
Title and meta description tags

Ex. title « Winicar | Buy a used and certified CITROEN DS3 »
Ex. description “A word from the seller: Joao S: “Vehicle almost new, very pleasant to drive!””
There are duplications despite the small amount of content. It is important to introduce deduplicating / unique elements in the titles (e.g. price)
Important keywords should appear as "early" as possible in the title tag. Here, Winicar should therefore be last, the model first.
The description is a little… descriptive here.
Example of title: “Citroën DS3 Noire 11700km at €18990 – Winacar”
Example of meta description “Buy a Citroën DS3 3 doors version 1.6 E-HDI 115 AIRDREAM SPORT CHIC. Used certified by Winacar experts and 3 month warranty.”
As said before, the challenge will be linking. And you have a huge amount of work to do on that before internal SEO optimization is really useful.

Technical Analysis of Poiscaille by Alexandre Madonna
The choice of technologies

Poiscaille seems to have chosen to build an entirely "homemade" PHP site rather than relying on an open source CMS.

Given that it is a fairly simple subscription platform whose added value is not at the technical level, I imagine that Poiscaille does not have a real CTO or internal technical team.

Based on this idea, for the initial version of the site, I would have rather opted for a site under WordPress (or other open source CMS) for several reasons:

The speed of deployment

It is generally easier to quickly put online (especially for SEO reasons) the basis of a site developed using a CMS (a few pages and articles) than to wait for the delivery of a custom development.

Captivity to the initial developer

In the absence of a CTO who is permanently involved in the project (a partner for example) and who would master the architecture, the maintenance and developments of the site will almost necessarily have to go through the initial service provider. It will be very difficult to transfer the management of the site to an agency without having it redeveloped...

Lack of functional scalability

This is the corollary of the previous point, with a homemade solution provided by a freelancer or an agency, the developments are dependent on the owner of the technology. On the other hand, a popular open source CMS has a plethora of free or paid plugins that any freelancer can deploy quite easily on a clean site, not to mention the possibilities of custom dev.

Uncertainty about the level of security

Even though open-source CMSs all have flaws, their level of use and the volume of their developer communities represent long-term guarantees that no single developer or small team can provide.

If I am not too mistaken about the lack of internal technical skills at Poiscaille, I am afraid that one day this site will have to be redeveloped using a new technology that is easier to maintain and evolve. My advice (purely technical) would then be to do it as soon as possible to avoid doing dev on the current site that would then have to be redone a second time on a new site! (edited)