Case study: internal links with Jev at ILOVEDIGITAL
On this website, we used Jev to compare semantic relationships between WordPress problem pages. Code gathered candidates and checked destinations; review determined what to publish. The delivered result improved navigation without claiming traffic or rankings had already increased.
· ILOVEDIGITAL Studio
The problem and candidates
Six problem pages contained detailed explanations but lacked a route from incident intervention to ongoing prevention. We compared all 30 directional pairs between the six pages, excluding self-links. Jev received existing public text and returned relevance probabilities for each relationship.
The model did not authorise publication
No pair reached the initial 0.80 automatic threshold. Source review approved five relationships pointing from incident pages to preventive maintenance. This does not mean a maintenance plan repairs an active incident. Model values helped order the review; they were not treated as proof of correctness or forecasts of Google ranking improvements.
What we published and checked
The manifest resolved the five relationships in the three languages with equivalent pages: Portuguese, Spanish and English. We published 15 links with local labels, existing destinations and no language changes. The release retained already published files. Its publisher completed 5,034 checks without failures, and we then confirmed all 15 public pages returned HTTP 200 with the new block in the HTML.
What the figures do not demonstrate
These checks establish delivery and working routes. They do not demonstrate more visits, enquiries or sales. Evaluating organic impact requires subsequent Search Console comparisons by page and query, accounting for reporting delays and other changes. This case documents the method and completed work rather than unmeasured commercial outcomes.