YouTube stopped being a place people visit just to kill time a while ago. It's the second-largest search engine on the internet, right behind Google itself. If you're putting out content there and simply hoping the algorithm notices, that approach runs out of steam fast.
What actually moves the needle is YouTube SEO — a deliberate set of practices that help your videos surface in search, get pulled into recommendations, and earn real visibility over time. This guide breaks down exactly what that means in practice and how to apply it step by step, whether you're starting from zero or trying to revive a channel that's gone quiet.
Why Migrations Lose Traffic
Almost never because the new site is worse. Almost always because URLs changed and the redirects were incomplete, chained, or pointed somewhere unhelpful.
The second most common cause is a staging configuration reaching production — a noindex tag or a robots.txt disallow that nobody removed.
Both are entirely preventable. Migration traffic loss is a process failure rather than a technical inevitability.
Before You Start
Crawl the existing site completely and export every URL. This is your inventory and everything downstream depends on it being complete.
Export Search Console data — every URL receiving impressions, and the queries driving them. Pages with traffic you did not know about are exactly the ones that get missed.
Export your backlink profile so you know which URLs have external links pointing at them. Those matter disproportionately.
Record current performance: rankings for priority terms, organic sessions by page, conversion by landing page. Without a baseline you cannot tell whether the migration hurt.
URL Mapping
Map every old URL to its new destination in a spreadsheet, one row per URL. No exceptions and no 'these will be fine'.
Map to the closest equivalent page, not the homepage. Bulk-redirecting removed pages to the homepage passes almost nothing and produces a poor experience.
Where there is genuinely no equivalent, decide deliberately: redirect to the parent category, or return 410 Gone. Both are legitimate; leaving it undecided is not.
Have someone who did not build the map review it. Errors in this document become errors in production.
Redirects Done Right
Use 301 for permanent moves. Each old URL should reach its destination in a single hop.
Flatten chains before launch. If your old site already contained redirects, the new ones stack on top and you end up with three or four hops, losing equity and eventually exceeding what crawlers will follow.
Test the full mapping against staging before launch. Every row, automatically. Manual spot-checking on a large site misses exactly the URLs nobody thought about.
Keep redirects in place indefinitely. Removing them after a few months discards the value they were preserving.
Launch Day
Check robots.txt first. Every single time. A disallow left from staging is the single most damaging thing that can reach production.
Check for stray noindex tags across templates.
Verify canonical tags point at the new URLs rather than the old domain.
Submit the new sitemap and keep the old URLs in a separate sitemap temporarily, so crawlers rediscover them and follow the redirects promptly.
The Weeks After
Expect some fluctuation. A short dip while the index updates is normal; a sustained decline is not.
Watch crawl stats and the index coverage report daily for the first fortnight. Spikes in 404s point straight at gaps in the mapping.
Compare Search Console query data against your baseline by page group rather than site-wide, so a decline in one section is not hidden by growth in another.
If It Has Already Gone Wrong
Crawl the old URL list and record what each returns now. Anything 404ing that used to receive traffic is a missing redirect and the first thing to fix.
Check for chains and flatten them.
Verify robots.txt and meta robots across templates before assuming a deeper problem, because the simple cause is usually the actual cause.
Recovery is normally possible when redirects are repaired, though it takes time. The longer broken URLs persist, the more of the accumulated value is lost.
Frequently Asked Questions
Almost always incomplete or chained redirects, or a staging configuration reaching production — a leftover noindex tag or robots.txt disallow.
No. Redirect to the closest equivalent page. Bulk redirects to the homepage pass little value and produce a poor user experience.
Indefinitely. Removing them discards the link equity and referral paths they were preserving.
robots.txt first, then stray noindex tags, then that canonicals point at the new URLs. A leftover staging disallow is the most damaging single failure.