données structurées schema.org comes up in nearly every audit we run. Rarely because the topic is complex: more often because it is handled last, once the budget is already spent.
Verify after every deployment
A correct configuration does not stay correct. A deployment, a hosting change or one new extension is enough to reintroduce a problem solved six months earlier.
An automated check at deploy time takes minutes to set up and prevents weeks of lost visibility.
The mistakes we see most often
Three mistakes recur with surprising regularity: applying a recommendation without checking it fits the context, changing several parameters at once which makes measurement impossible, and giving up after six weeks because nothing moved.
The third is the most expensive. Effects are rarely visible before a full recrawl and re-evaluation cycle, which often takes two to three months on a mid-sized site.
The real cost of doing nothing
An untreated technical problem does not stay stable: it spreads. Every new piece published on a faulty structure inherits the defect, and remediation cost grows with volume.
That is why fixing a structural flaw on a hundred-page site beats waiting until you have a thousand. The work is the same; the cleanup is not.
The role of HTTP headers
Status codes, cache headers, canonicals sent as headers: a significant share of technical signals lives not in the HTML but in the server response.
It is also where errors stay unnoticed longest, since they have no visible effect on screen.
What the engine actually sees
Before optimising anything, look at the page as the crawler receives it, not as the browser displays it. The gap between the two often explains months of unexplained stagnation.
Simply comparing the rendered source with the initial source reveals in minutes whether essential content depends on execution the engine does not guarantee.
Prioritise before fixing
An audit always produces more recommendations than it is reasonable to act on. Sorting happens on two axes: how many pages are affected, and how deep the problem sits in the chain.
An error blocking crawling comes before an improvable tag. Fixing the order costs more than fixing the content.
Check before moving on
- Remove before adding
- Check the rendered source, not just the display
- Automate every repetitive check
- Document the decision, not just the action
- Schedule a review in six months
- Handle what affects the most pages first
Read next
- Sitemap XML : la carte que vous donnez aux moteurs
- robots.txt : le fichier le plus mal utilisé du web
In practice
Bring this list to your next weekly review and assign each item to a person, with a deadline. A technical topic without an owner stays an untreated technical topic.
