What this project is
This project is a full website redesign combined with a platform migration — commonly called a replatforming. The site moves from WordPress to a static site architecture: pre-built HTML, CSS and JavaScript pages served directly from hosting. The approved new design is the target; the current site’s content, URLs and search equity are the foundation.
The most important rule of this project: nothing that already works gets lost. Everything that has been optimized carries over:
The result: a faster website that is easier to look after — while everything Google already likes about the current site comes along, instead of starting over.
Scope: every page, counted
We checked every page on the dev/staging site on 30 September 2026. The full count came to 371 pages:
| Page group | Pages | What happens |
|---|---|---|
| Main pages (home, roles, industries, services, about, legal, tools) | 109 | Rebuilt on the new design |
| Blog posts | 83 | Moved under the new /blogs/ section, with dates, authors and links kept |
| Service-area pages (states & provinces) | 65 | The local search pages, incl. the service-areas hub |
| Recruiter location pages | 63 | The newest pages, ready and waiting to launch |
| Job overviews | 36 | Moved over exactly as they are |
| Blog category pages | 15 | Rebuilt as listing pages in the new blog section |
| Total | 371 | Every page is listed and moved — none are skipped |
Where the 371 comes from: 294 pages are on the website today, 63 recruiter pages are ready and waiting to launch, and 14 more pages already sit on the dev/staging site but don’t show in the public page list yet (newer pages, utility pages and a few still being prepared). Together: 294 + 63 + 14 = 371.
The dev/staging site always has the newest version of every page — the live website gets updated from it. We count from there so nothing that’s ready to launch gets missed.
Who does the work & where the site lives
One person runs this project from start to finish: Annie Lynn Simoy, SEO & GEO Specialist, working 20 hours a week. Modern AI tools help speed up the heavy lifting, and a real person checks and approves every page before the site goes live.
The 12-week schedule has two clear parts: weeks 1–4 complete the full site migration, and weeks 5–12 are SEO + GEO work to grow rankings after launch.
Hosting: Hostinger — already yours
The new site will live on the client’s existing Hostinger account. No new hosting company is needed, and nothing changes with the website address, email, or security. On launch day, the new site simply replaces the old one on the same account.
Web addresses & redirects
The address plan is simple on purpose. Every page on the new site gets the same address it has today — a 1-to-1 match. The one exception: all blog posts move under /blogs/ (for example, easy-outsource.com/blogs/post-name/), and each old blog link will automatically forward to its new home in the blog section.
| Address situation | What we do |
|---|---|
| All pages except blog posts | Keep the exact same address — nothing changes for visitors or Google |
| Blog posts (83) | Move under /blogs/ — each old address gets one simple automatic forward (a “redirect”, like mail forwarding when you move house) |
| Blog category pages (15) | Rebuilt as listing pages in the new blog section |
| Addresses that already redirect today | Keep working exactly the same way — now handled by the hosting, which is faster |
| Additional redirects already planned | Old addresses pointing to the right current pages — checked in week 1 and built into the same redirect file |
| Addresses with extra tags on the end (like ?role=writer) | Keep pointing to the same main pages as they do today |
| Pages deleted or merged | None. Nothing goes away in this project |
Why this matters: when a page keeps the same address, the same words and the same dates, Google doesn’t have to relearn anything. The whole move is designed so that, from Google’s point of view, as little as possible changes at once — only the speed and the look improve.
The plan, step by step
Nine steps over 12 weeks, done by one person at 20 hours a week, with AI tools helping to speed things up. The first four weeks are the full site migration (steps P1–P7, launch in week 4); the eight weeks after are SEO + GEO work (steps P8–P9).
| Step | When | What happens | Hours |
|---|---|---|---|
| Full site migration · Weeks 1–4 | |||
| P1 · Start-up: page list & address plan | Week 1 | Confirm the full list of 371 pages, lock the 1-to-1 address plan, review and prepare the redirect lists — the redirects in use today plus the additional planned redirects, with time to review any other pages that may need one — and save a record of today’s Google results to compare against after launch | 4 |
| P2 · Build the private preview | Week 1 | Set up staging on Hostinger with search-engine blocking, deploy the approved design’s file structure, connect analytics, tag management and the CRM lead flow | 4 |
| P3 · Page layouts & blog move | Week 1 | Build the shared page layouts (main pages, roles, services, local pages, blog) — including the shared header with a full menu of roles, industries and services, and the footer — and the way content moves into them; move the blog posts under the new /blogs/ section, with each old blog link set to forward to its new address; make one sample page of each type for approval before building all the rest | 12 |
| P4 · Move all 371 pages | Weeks 2–3 | Move the pages over in groups — the local pages first, then roles, services and industries, blog posts (at their new /blogs/ addresses), then legal and utility pages — with every group checked before the next one starts | 40 |
| P5 · Google setup | Week 4 | Titles, descriptions and Google-friendly page info (schema) on every page; the sitemap and robots file (the page list and instructions Google reads); the redirect file — old links that automatically forward, including the blog moves and the additional planned redirects prepared in week 1 | 4 |
| P6 · Full check before launch | Week 4 | Check every single page, test every form and the booking flow from start to finish, test on real phones and computers, run speed tests, write and sign off the switch-back plan, and check that Google Analytics, tag management and the CRM lead flow are all working | 4 |
| P7 · Launch | Week 4 | Switch the new site live on Hostinger, remove the “hide from Google” setting and check it worked, send the sitemap to Google and Bing, run one live lead test, review analytics and conversion tracking, and run final speed checks | 8 |
| SEO + GEO work · Weeks 5–12 | |||
| P8 · Stabilize & hand over + SEO work | Weeks 5–8 | Watch the site closely every day at first and fix anything that needs it; prepare a report comparing Google results before and after the move; write a simple how-to guide for the new site; ongoing SEO improvements | 80 |
| P9 · SEO + GEO work | Weeks 9–12 | Improve how existing pages rank on Google, make the site easy for AI assistants (like ChatGPT) to find and recommend, and identify new pages worth creating | 80 |
| Total | 12 weeks | 20 hours a week — 4 weeks of migration + 8 weeks of SEO + GEO work | 236 |
Checks before launch
Each step must pass its check before the next one starts. That is what makes a 371-page move safe at 20 hours a week.
Checks between steps
- Address plan locked (P1): no page gets built unless it’s a line in the address plan — and every line gets built.
- Sample approval (P3): one sample page of each type is reviewed and approved before all the others are made.
- Group checks (P4): every group of pages is tested — links work, info is correct, dates are correct — before the next group starts.
- Ready-to-launch check (P6): the full site check, the form and booking tests, the phone and computer tests, and the signed switch-back plan all pass before launch day is booked.
Launch day checklist
- Launch is a simple switch on the client’s own Hostinger account — the web address, email and security stay untouched
- The “hide from Google” setting is removed and checked on the live pages, not just in the files
- A quick test of old links: each one forwards in a single step to the right place
- The updated page list (sitemap) is sent to Google and Bing, and Google is asked to look at the important pages right away
- One real form submission and one real booking tested on the live site
- Switch-back plan ready before launch: if anything goes wrong, the previous site can be switched back quickly
- Every page checked after launch: no broken links, no wrong forwards
How we protect your Google results
This plan is built around one simple idea: the less that changes for Google, the less there is to lose.
- Same addresses. Every page keeps its exact address — except blog posts, which each get one simple automatic forward from their old address.
- Same words, dates and Google info. The copy, the publish dates, the titles and descriptions, and the behind-the-scenes page info all carry over — the history the site has built is kept, not reset.
- Same forwards. The redirects the site uses today keep working exactly as before, just faster.
- Measured, not guessed. We save a full record of today’s Google results before starting, then compare after launch, group by group — so any change is spotted and fixed early, with proof.
Even when everything above is done right, Google results can go up and down for a few weeks after a big change like this. This plan is built to keep that window as short as possible. We can’t promise exact rankings or dates — but we can promise that every protection available is in this plan, and that results are watched every day at launch and every week after until they are steady.
What we need from you
- Access at the start: the Hostinger hosting account, Google Analytics, Google Tag Manager, Google Search Console, and the form/CRM settings. No domain or address changes are planned — access is just for checking.
- Quick approvals: feedback within two business days during review weeks keeps the 12-week schedule on track.
- A launch morning: pick a quiet weekday morning for going live.