The challenge
itilite's website is a large B2B SaaS site: about 1,600 pages, including around 1,300 blog posts. It was moving from WordPress to Webflow. On a site this size, every broken URL, missing image or lost tracking tag costs visitors and leads, and problems are easy to miss.
What I did
I prepared and led the migration, and I now look after the site's technical SEO, speed and monitoring.
- Planned the redirect map before launch. 1,284 of 1,301 blog posts (98.7%) kept their URLs, and moved posts were redirected. I also moved a 122-article Help Center to Webflow with 57 redirects.
- Cleaned up at scale. 1,746 alt-text updates, about 5,190 internal links fixed, a footer link that was broken on 1,593 pages fixed, and all 1,615 sitemap entries returning clean.
- Built weekly monitoring. A crawler checks about 1,600 pages and 285,000 links in 8 ways. A speed report covers 37 key pages using lab and real-user data, and real-user speed tracking runs on every page. Everything reports to the team every Monday.
- Fixed what was costing leads. Found and fixed dead demo buttons on 25 live pages, and restored demo conversion tracking.
- Prepared the site for AI search tools. An AI-readable fact sheet, a data methodology page and an llms.txt file.
- Built a free US per diem calculator. A main page plus 49 state pages on official GSA rates, with tested calculation rules.
How I checked it
Nothing is assumed fixed until it's checked on the live site. The weekly crawler re-checks failures before reporting them and ignores partial crawls, so the team only sees real problems. The per diem calculator's rules are covered by fixed test cases, and all 50 of its pages were checked on the live site for status, headings, canonical tags, tracking and mobile layout.
Working safely with AI
AI makes repetitive work fast, but on a live company website it needs guardrails:
- Restricted connector permissions: the AI can't publish or change site settings.
- A change log with the old value for every edit, so any change can be reversed exactly.
- A backup before every bulk change.
- People publish, never the AI.