---
title: "Comment by Rishabh Mishra on \"The Redirect Map That Protects WordPress Rankings\" | Hashnode"
description: "The step most people skip is the post-move sweep of hardcoded URLs in widgets and custom fields. A serialized-safe search-replace fixes the database, but a quic"
url: "https://hashnode.com/posts/the-redirect-map-that-protects-wordpress-rankings/6afdf3eaf6a65c6e2ad459d9/comment/6affb8e326566e209e6830d1"
---

[Discussion](https://hashnode.com/posts/the-redirect-map-that-protects-wordpress-rankings/6afdf3eaf6a65c6e2ad459d9)

Comment [The Redirect Map That Protects WordPress Rankings](https://hashnode.com/posts/the-redirect-map-that-protects-wordpress-rankings/6afdf3eaf6a65c6e2ad459d9)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[2d ago](https://hashnode.com/posts/the-redirect-map-that-protects-wordpress-rankings/6afdf3eaf6a65c6e2ad459d9/comment/6affb8e326566e209e6830d1)

The step most people skip is the post-move sweep of hardcoded URLs in widgets and custom fields. A serialized-safe search-replace fixes the database, but a quick crawl of the new site for any remaining old-domain strings catches what the plugins leave behind. Running that crawl before removing the noindex is the cheapest insurance in the whole sequence.

[techpotions](https://hashnode.com/@techpotions)

[2d ago](https://hashnode.com/posts/the-redirect-map-that-protects-wordpress-rankings/6afdf3eaf6a65c6e2ad459d9/comment/6affb8e326566e209e6830d1#reply-6b005eaa72c431734a44c4dd)

Exactly, that’s the step the plugins quietly let you skip. The serialized-safe search-replace handles the database, but widgets, custom fields, and page-builder meta keep their own hardcoded copies that a raw query never touches. And your ordering point is the sharp one: crawling for old-domain strings while the noindex is still up means you catch the leftovers before Google ever sees them, no downside, huge upside. We treat that crawl diff as the real go/no-go gate, if it isn’t clean, the cutover waits. Great add.
