To check rankings after a site migration, compare pre-migration keyword positions against post-migration movement, then isolate losses by page, keyword group, device, and location. The goal is not just to see if rankings dropped, but to identify which URLs lost visibility, whether the right new pages replaced the old ones, and what technical issues are blocking recovery.
A migration can change URLs, templates, internal links, canonicals, content, and crawl paths all at once. That means rank checks need to be structured. If you only look at a few head terms, you can miss the real problem: entire keyword clusters slipping because redirects, indexation, or page relevance changed.
Start with a pre- and post-migration ranking baseline
The fastest way to measure migration impact is to compare the same keyword set across three points: before launch, immediately after launch, and 2 to 6 weeks later. This shows the difference between temporary volatility and a real visibility loss.
Build your baseline around keywords that matter to revenue or leads, not just vanity phrases. For example, if a local service business migrated from old city pages to a cleaner folder structure, you would want to track terms like:
- primary service keywords
- location-modified keywords
- brand terms
- high-converting long-tail queries
- keywords mapped to pages that changed URL
If you already use a ranking tool, export your tracked keywords before the migration. After launch, reload the same set and compare movement by landing page. A rank tracking view is especially useful here because it shows whether a keyword drop is tied to one page, one template, or the whole site.
Check whether old URLs transferred rankings to the correct new URLs
One of the most common migration problems is that rankings do not disappear completely; they shift to the wrong page or fail to transfer at all. A page that ranked in position 4 before the migration may now redirect to a broader category page that only ranks in position 18 because the search intent no longer matches.
Review your highest-value migrated URLs one by one:
- old URL
- intended new URL
- actual redirect destination
- current ranking URL
- keyword set previously associated with that page
If the ranking URL is different from the intended destination, that is a signal to inspect redirect logic, canonicals, internal links, and on-page relevance. Search engines may be choosing a different page because your migration weakened topical clarity.
What a clean URL mapping check looks like
For a blog article that used to rank for “technical seo checklist,” the old page should redirect directly to the closest updated equivalent. If it redirects to a generic blog hub instead, rankings often soften because the destination no longer satisfies the original query as precisely.
Old URL: /technical-seo-checklist-2023
301 Redirects To: /blog/technical-seo-checklist
Expected Ranking URL: /blog/technical-seo-checklist
If Actual Ranking URL: /blog/
Then inspect redirect target, canonical tag, internal links, and content match.Segment ranking drops by page type, not just by keyword
After a migration, broad averages can hide the source of the problem. A site may look down only 8% overall, while product pages are down 35% and blog pages are flat. That leads to very different fixes.
Group rankings by page type such as:
- product pages
- category pages
- service pages
- location pages
- blog content
Then compare which page groups lost the most positions and clicks. If only one template dropped, the issue is often structural: missing metadata, changed heading hierarchy, weaker internal links, blocked resources, or a template-level canonical error.
Use Search Console to confirm visibility changes beyond rank tracking
Rank tracking tells you where monitored keywords moved. Search Console helps you spot broader query and page-level changes, including terms you were not actively tracking before the migration.
Look at these reports first:
- Pages with the biggest drop in impressions
- Queries that lost average position after launch
- Pages that gained impressions but lost clicks due to lower CTR
- Indexed pages that should have been replaced by new URLs
A practical example: if your old buying guide used to rank for 40 long-tail queries and the new version now ranks for only 12, the issue may not be a total deindexation problem. It may be that the migrated page lost supporting copy, FAQ content, or internal links that previously helped it rank for variations.
Compare desktop, mobile, and local rankings separately
Migration issues do not always affect every search result equally. A redesign may preserve desktop rankings while mobile positions fall because content moved lower on the page, Core Web Vitals worsened, or key copy was hidden in tabs.
Local businesses should also compare rankings by city or ZIP-level target area if location pages were changed. A page can hold steady in one city and drop sharply in another if local modifiers, internal links, or unique location content were removed during migration.
This is where Ranktracker can be useful in a practical way: instead of checking a few keywords manually, you can monitor movement by device and location to see exactly where migration losses are concentrated. That makes recovery work much faster because you are not guessing which segment broke.
Audit the technical issues most likely to cause ranking loss
If rankings dropped after the migration, the next step is to connect those drops to a technical cause. Focus on the issues most likely to affect transferred relevance and crawlability.
Redirect chains and wrong-status pages
Every important old URL should return a clean 301 to the best matching new URL. Chains, loops, 302s, and soft 404s often weaken ranking transfer.
Canonical tags pointing to the wrong version
If new pages point canonicals to old URLs, staging paths, parameterized versions, or generic parent pages, search engines may ignore the page you want ranked.
Internal links still pointing to old URLs
Redirects help users reach the right page, but internal links should be updated to the final destination. If your navigation, breadcrumbs, or contextual links still point to redirected URLs, you waste crawl signals and slow consolidation.
Indexation conflicts
Check for accidental noindex tags, blocked folders, duplicate versions, and XML sitemaps that still list retired URLs. A migration often creates mixed signals when old and new versions coexist too long.
Warning: Do not judge a migration only by homepage rankings. Many migrations appear stable at the top level while deeper money pages lose visibility because of redirect mismatches or weakened internal linking.
Match ranking losses to likely fixes
Once you know which keywords and pages dropped, assign a likely cause and action. This keeps the recovery process focused.
- Old URL ranks instead of new URL: improve redirects, canonicals, sitemap updates, and internal links.
- New URL ranks lower than old URL did: restore missing content depth, headings, schema, and intent match.
- Only mobile rankings dropped: review page speed, layout shifts, hidden content, and mobile UX changes.
- Only local terms dropped: restore city-specific relevance, local internal links, and unique location copy.
- Only one template dropped: inspect template-level metadata, canonicals, robots directives, and content placement.
Set a realistic post-migration monitoring schedule
Rankings often fluctuate for a short period after launch, but you need a schedule that separates normal reprocessing from a deeper issue. A simple monitoring plan works well:
- Days 1 to 3: verify redirects, indexation, canonicals, and top keyword movement
- Week 1: compare top landing pages and keyword clusters against baseline
- Weeks 2 to 4: watch whether lost rankings begin transferring to the intended new URLs
- Weeks 4 to 8: treat persistent losses as a recovery project, not temporary volatility
If your rankings are still materially down after several weeks and the wrong pages are appearing in results, the migration likely introduced structural relevance or technical problems that need direct correction.
What a successful ranking check should tell you
A useful post-migration ranking review answers four questions: which keywords dropped, which pages lost visibility, whether the correct new URLs replaced the old ones, and what issue is preventing recovery. Once you have those answers, the next steps become clear.
For beginners and site owners, the key is to avoid checking rankings in isolation. Pair keyword movement with URL mapping, page type analysis, and technical validation. If you track rankings consistently before and after launch, you can catch migration losses early and recover faster instead of waiting for traffic reports to reveal the damage.