-
Until 28 September 2026
1 · The starting point
The site was static HTML. I published by editing files. In July 2026 Search Console showed 316 impressions and 4 clicks. The address pattern was<number>-<slug>.htmlunder/news/. It worked, but I wanted a CMS and a cleaner address structure without losing what search had already found. -
August 2026
2 · Preparing the move
I fixed the technical debt before the move. The work was boring, and that was the point.
Internal links209in 142 texts; missing trailing slashAlt text367 imageswritten in August 2026Sidebar layout bug400 of 406affected pages fixedHeader height136 pxon all 17 tested widthsResponse time without cache60–90 seconds → 0.2–0.3 secondsnew site before the move, uncached, under parallel load -
Migration day
3 · Moving day (28 September 2026)
The site moved to WordPress. The address structure changed from/news/<number>-<slug>.htmlto/news/<slug>/. I checked 1,516 URLs and found zero errors. 745 old URLs now redirect once, with a 301, to the new address. -
July – October 2026
4 · Growth
Search Console shows the line after the move. Impressions: 316 in July 2026 → 1,339 in August → 2,664 in September → 3,886 in October (days 1–23). Clicks: 4 → 32.
Google Search impressions and clicks, July 2026 → October 2026 · October: days 1–23 Impressions ClicksSource: Search Console, monthly totals. October 2026 — days 1–23 ┆ -
What changed
5 · What it shows
A move is a risk for search. The risk is in the details: old addresses, internal links, redirects. I checked 1,516 URLs and set one 301 redirect for 745 old URLs. The new structure is/news/<slug>/. Impressions grew from 316 to 3,886, and clicks from 4 to 32. That is the method I bring to your store: check each address, then watch the result in Search Console.
Treat a move as a list of addresses, not a leap of faith. Check each one, redirect old URLs once, and keep the result visible in Search Console. That is what I bring to your store.