A visual brief on what changes, what stays, and what we control. Read in five minutes; decide with confidence.
Migrations always carry SEO risk. Ours is small, planned for, and reversible.
Expect a 10–30% dip for ~30 days, then recovery and growth past today's baseline.
Every URL on padmashreecollege.edu.np stays identical. Google sees no change.
Every migration that loses SEO falls into one of these traps. We address each with a specific, testable safeguard before any code is deployed.
If /blog/admission becomes /blogs/admission, Google sees a brand-new page. Rankings, backlinks, authority — all start from zero.
Even a perfect migration causes a 10–30% traffic dip while Google re-crawls and re-trusts the new infrastructure. Normal. Recovers in 2–6 weeks.
If hand-written page titles aren't carried over, Google sees "different content" and may re-rank. Years of SEO work, gone.
meta_title, meta_keywords, meta_description columns. Ported verbatim. Zero regeneration.
Old Blade templates may have hardcoded paths. If any survive into production, they 404 — which Google notices and penalizes.
If image paths shift, Google Image Search rankings drop. Currently your images live at /uploads/blog/abc.jpg.
Submitting a fresh sitemap with different URLs and no redirects = Google deindexes the old ones.
Pulled directly from your routes/frontend.php. Every public URL maps 1:1 to a Next.js route. Google sees zero change.
A typical, well-executed migration follows this shape. The dip is real but short; the gain is structural and lasting.
Page speed and Core Web Vitals are direct ranking signals. Today's site likely scores 50–70 on Lighthouse. The new one targets 90+. That difference is measurable in rankings.
| Dimension | Today (Laravel + Blade) | After (Next.js 15) | SEO impact |
|---|---|---|---|
| Page load | 3–5s typical | < 2s LCP | Mobile rankings |
| Render strategy | PHP per request | RSC + ISR cache | Lower TTFB |
| Image format | JPG / PNG | AVIF / WebP auto | Image search |
| Structured data | None / partial | Course, Article, Event, FAQ | Rich results |
| OG / social cards | Single site image | Per-page dynamic | Higher CTR |
| Sitemap | Manual / static | Auto, fresh on every deploy | Faster indexing |
No big-bang. Stage, verify, switch, monitor. The same playbook BBC, Shopify, and Vercel themselves recommend.
Build everything on staging.padmashreecollege.edu.np. Block search engines with X-Robots-Tag: noindex. Test thoroughly. Old site stays live.
Automated script crawls today's site, produces existing-urls.txt. Every URL must resolve HTTP 200 on staging — or have a documented 301. Deploy is blocked otherwise.
Switch DNS at low-traffic hour (typically 02:00–04:00 local). Old site goes off, new site goes live at the same domain. Google starts crawling within minutes.
Re-submit sitemap. Use "URL Inspection → Request Indexing" on top 20 pages. Monitor Coverage report daily. Watch for unexpected 404s.
Watch Search Console Performance: clicks, impressions, position. Core Web Vitals should improve immediately. By day 30, traffic is back to baseline; by day 60–90, above it.
Each item is verified by automation, not promise. CI fails if anything is incomplete.
The migration is bounded, planned, and reversible. Done with these safeguards, your SEO doesn't just survive — it gets faster, more structured, and more visible than it is today.