We reviewed 246 codesrc.ru articles, prepared 138 possible redirects and planned 54 topics. This case explains how we checked existing content and divided new assignments among authors.
Project website: codesrc.ru
What needed to change
Before preparing a new plan, we needed to review published articles and old URLs. This helped avoid repeated topics and turn technical issues into specific developer tasks.
We reviewed public articles, the catalogue and author profiles. CMS drafts were outside the review. Search demand was assessed separately, without treating query frequency as a traffic forecast.
Work and results
| Work | Result | Period or source |
|---|---|---|
| Articles, old URLs and 404 errors | 246 articles checked | September 2026 |
| An article plan for nine authors | 54 topics included in the plan | September 2026 |
Articles, old URLs and 404 errors
246 articles checked · September 2026
We reviewed the archive of 246 articles and old URLs. We listed 138 redirect candidates and prepared a technical brief for the developer.
Each redirect needs a suitable destination page. An old URL alone is no reason to send visitors to the homepage.
This stage produced a list and a brief. Implementation of all 138 redirects has not been confirmed.
An article plan for nine authors
54 topics included in the plan · September 2026
For the plan, we examined 246 articles, 61 catalogue pages and nine author profiles. We compared titles and content with the previous plan to avoid overlapping assignments.
We prepared 54 topics, six for each of nine authors, and checked demand for 77 queries. Each assignment states what the reader should learn and how the article differs from related content.
We checked 108 links in the plan. We found differences between public author bylines and API data and listed them in a table. We added a new author and published their profile.
Dates in the plan are a proposed schedule. A completed brief does not mean the article has been written or published.
How we checked the results
We checked the technical work against the published archive and old URLs. The editorial review used current articles, author profiles and the previous plan.
Demand was checked in Wordstat for Russia over a recorded period. The values include word forms and query groups; they cannot be added together as a traffic forecast.
The screenshots show the current public blog on desktop and mobile. Internal assignments and team documents are not presented as published articles.
What to keep in mind
The 138 URLs are redirect candidates. After implementation, each response code and final page needs checking.
The 54 topics are a prepared plan. This case does not confirm publication of all articles or a resulting increase in traffic.
Before similar work
For blog work, record separately what has been reviewed, which briefs are ready and which changes are live. This keeps plans and proposals distinct from completed implementation.