The problem: Change in trend with a loss of 50% of organic traffic.
Problem start date: May 25, 2022
Where the problem occurs: In several verticals systematically.
The closest and most accurate data source is analyzed, which is Search console. Both at a general level, and for each vertical, and typology.
A chronological map is made of the last implemented tasks that may be related to traffic loss in order of impact.
A check is carried out for serious technical errors that could have caused these changes.
The logs are analyzed to see where there is a loss or excessive increase in tracking.
We brainstorm general and specific solutions for each problem in order to have the full range of solutions to implement. In this case these were some of the tasks posed:
Perform spintax to quickly remake certain types of content
Curation of content from relevant clusters
Prioritizing content improvements on specific urls
Review of anchoring and internal linking patterns
Fix various ux issues
Expand content of thin content urls
Elimination of detected cannibalizations
Deindex urls without SEO guidance
Redo a repetitive internal linking block that makes no SEO sense
n this section we evaluate all the viable tasks, and we discuss how to approach them in the best way. We make an evaluation of how much of the problem it solves, development time, and impact. In short, evaluate the proposed solutions in terms of feasibility, cost, impact and alignment with the objectives and available resources. It is important to consider the pros and cons of each solution.
In this case the final order was:
Deindex URLs without SEO meaning
Expand thin content Perform spintax of the repetitive clusters (the most important)
Curation of content from relevant clusters
Prioritizing content improvements on specific urls
Review of anchoring and internal linking patterns
Fix various ux issues
Redo a repetitive internal linking block that makes no SEO sense
Eliminate Cannibalizations
In order to have control of each implementation, effectiveness, and results, the variables must be isolated. Therefore, implementations are planned in order to monitor and evaluate each one. In this way at Roilab we can also improve, learn and continue expanding our knowledge based on each experience.
We emphasize that the 3rd task on spintax was the one that gave the best results and largely resolved the problem for this client.
In subsequent tasks, content improvements have been implemented through custom implementations with artificial intelligence.