Minicor moved its blog in July 2026 and many posts got new addresses. The old ones were never redirected. The RSS feed the main sitemap still lists, /feed.xml, stops at April 13, 2026 and links to 51 old addresses. 29 of those are missing from the current blog sitemap, and nine we opened return 404. They include the posts that make the core sales case: "Going from Zero to Production in Three Weeks", "Computer Use Agents vs Traditional RPA" and "How to Automate Software With No API". Readers, feed subscribers, search engines and AI assistants that follow those links hit a dead end. Meanwhile a working feed at /blog/rss.xml carries every post up to October 20.
First action
Export the 51 links from /feed.xml and match each one to a live slug in /blog/sitemap.xml.
How to measure it
Dead legacy blog URLs
- Now
- –
- Target
- 0 of 51
- By
- 2 weeks
Steps
List old addresses
All 51 links from /feed.xml plus any old slugs in Search Console's 404 report.
Co-Founder and CEO 2 hours
Map to live posts
Match each to the same article under its new slug, or to the closest live guide.
Co-Founder and CEO 1 day
Add 301 redirects
In the Next.js redirects config or the blog platform, using the same mechanism as the one Athena redirect that already works.
Software Engineer half a day
Swap the feed
Redirect /feed.xml to /blog/rss.xml and list the live feed in the main sitemap.
Software Engineer 1 hour
Republish the keepers
Bring back the zero-to-production story and the RPA comparison as current posts.
Co-Founder and CEO 1 week
Check and monitor
Re-crawl all 51 addresses; watch Search Console's 404 and redirect reports monthly.
Software Engineer monthly
Why it works
Map each of the 51 old addresses to its current post. Many are the same article under a new slug: /blog/automate-software-no-api is now /blog/guides/how-to-automate-software-with-no-api, and /blog/two-models-click-accuracy is now /blog/split-reasoning-from-grounding-why-two-models-beat-one. Add 301 redirects. Where a post was retired, redirect to the closest live guide, and republish the ones worth keeping, starting with the zero-to-production story and the RPA comparison. Then make /feed.xml redirect to /blog/rss.xml (or serve the same content) and list the live feed in the sitemap. One old address already redirects correctly, so the mechanism exists. It just needs the full map.
Links and rankings the old posts earned between December and April pass to the live pages instead of being lost. Feed readers and aggregators start getting every post published since the move. It costs a day of work and protects the content engine that is Minicor's main source of inbound interest.
Ready to use
ChecklistBlog redirect map, first entries
/blog/automate-software-no-api -> /blog/guides/how-to-automate-software-with-no-api /blog/two-models-click-accuracy -> /blog/split-reasoning-from-grounding-why-two-models-beat-one /blog/ai-agents-legacy-software -> /blog/how-ai-agents-work-with-legacy-software /blog/self-healing-automation -> /blog/self-healing-automation-what-it-means /blog/citrix-remote-desktop-automation-ai-agents -> /blog/citrix-and-remote-desktop-automation-with-computer-use-agents /blog/ai-bottleneck-legacy-system-deployment -> /blog/the-bottleneck-is-not-ai-capability-it-is-legacy-system-deployment /blog/automate-sap-gui-legacy-erp-desktop -> /blog/guides/automate-sap-gui-legacy-erp-desktop /blog/automate-cdk-global-dealer-management-system -> /blog/guides/automate-cdk-global-dealer-management-system /blog/zero-to-production-three-weeks -> republish, then redirect /blog/computer-use-agents-vs-traditional-rpa -> republish, then redirect /feed.xml -> /blog/rss.xml
Risks and how to handle them
Redirect chains or loops
Point every old address straight to its final live URL and test each one.
Mapping to the wrong article
Match on titles first; send unclear cases to the closest guide, not the homepage.
Evidence
- Your websiteRSS feed /feed.xml, listed in the main sitemap (checked November 9, 2026): 51 items, newest dated April 13, 2026. 29 of its 51 post addresses are not in the current blog sitemap, and nine we opened return "404 Not Found", including "Going from Zero to Production in Three Weeks" (/blog/zero-to-production-three-weeks), "Computer Use Agents vs Traditional RPA: A Practitioner's Comparison" and "How to Automate Software With No API" (/blog/automate-software-no-api). One old address, /blog/automate-athena-ehr-without-api, still opens its article. A current feed exists at /blog/rss.xml (50 items, newest October 20, 2026).Source
- Your websiteBlog: 55 posts on one page with "All" and "Guides" tabs and a search box, dated July 8 to October 20, 2026, including "Why AI Companies Lose Deals (It Is Not the AI)", "Audit Trails for Automated EMR Writes: What Regulated Buyers Require", "What Computer Use Benchmarks Measure, and What They Miss", "Run Desktop Automations in Parallel Without Collisions" and "MFA in Unattended Desktop Automation: Production Guide"; no newsletter signup and no author names on the index; footer "Powered by Revnu"; a separate blog sitemap lists 57 URLs.Source
- Your websiteMain sitemap (134 URLs, checked November 9, 2026): 111 use-case pages, 9 system FAQ pages (Epic, Oracle Health Cerner, athenahealth, Manhattan, Blue Yonder, HighJump/Körber, SAP GUI, Oracle Forms, Sage 300), one newsroom post, /llms.txt and /feed.xml; no pricing page, no customer stories or case studies and no comparison pages.Source