Should you really include old HTTP URLs in the sitemap when migrating to HTTPS?

Why does Google recommend submitting old HTTP URLs?

The reasoning behind this recommendation relates to how Googlebot handles site migrations. When you transition from HTTP to HTTPS, you technically create a new site in Google's eyes. 301 redirects allow for authority transfer, but the bot still needs to crawl those URLs to discover the redirects.

By submitting old HTTP URLs via sitemap, you create explicit entry points for Googlebot. The bot will crawl these URLs, encounter the 301s, follow the redirects to HTTPS, and understand that this is a site transfer. Without this active submission, Google relies on its usual sources of discovery: internal and external links, crawl history, user signals.

Does this approach apply to all HTTPS migrations?

This recommendation mainly targets sites with a significant volume of URLs or a complex structure. For a site with 20 pages and strong backlinks, Googlebot will naturally discover the redirects in a few days. However, for an e-commerce site with 50,000 products or a media site with deep archives, re-crawling can take weeks without assistance.

The distinction between submitting the sitemap on the old HTTP property or the new HTTPS is minor in practice. What matters is that the HTTP URLs are explicitly listed to trigger the crawl. Google indicates that both approaches work, suggesting flexibility in implementation.

How long does this submission remain useful?

The utility window is during the active transition phase, usually 2 to 6 weeks following the migration. Once Google has crawled the majority of the redirects and consolidated signals towards HTTPS, maintaining old URLs in the sitemap loses its relevance.

Some SEOs leave the HTTP sitemap in place indefinitely out of caution, but this can create unnecessary confusion in the long term. After full consolidation (verifiable via coverage reports and server logs), it's cleaner to remove the HTTP sitemap and maintain only the HTTPS version.

• Submitting HTTP URLs speeds up Googlebot's discovery of the 301 redirects
• This approach works whether the sitemap is submitted via the old HTTP property or the new HTTPS
• This practice is especially critical for sites with a large volume of URLs or a complex structure
• The submission remains useful during the transition phase (2 to 6 weeks) and can then be removed
• Without active submission, re-crawling depends on usual sources and can take significantly longer

Is this recommendation consistent with field observations?

Yes, absolutely. Poorly managed HTTPS migrations consistently show periods of fluctuation where organic traffic temporarily drops. Sites that actively submit a sitemap of old URLs regain their visibility 40 to 60% faster than those relying solely on passive redirects.

Server logs confirm this dynamic: when you submit an HTTP sitemap, you see a spike in Googlebot crawling within the next 48-72 hours, focused on those URLs. Without submission, re-crawling follows the usual frequency of each URL, which can mean months for deep pages with low crawl budgets.

What nuances should be added to this statement?

Google remains vague on the optimal duration for maintaining the HTTP sitemap. The phrase “will accelerate the process” does not provide any quantifiable benchmarks. [To be verified] on large volumes, but field feedback suggests that beyond 4-6 weeks, the marginal impact becomes negligible.

Another point not mentioned: this technique works better if the 301 redirects are clean (1:1, no chains, correct HTTP status). If your redirects are broken or chained, submitting a sitemap of old URLs will only expose the problem faster. The submission accelerates discovery but does not correct implementation errors.

In what situations could this approach cause problems?

If you submit a sitemap containing thousands of obsolete HTTP URLs leading to non-existent or 404 error HTTPS pages, you waste crawl budget and send confusing signals. Google will crawl aggressively, encounter errors, and potentially slow down the crawl of valid URLs.

Be cautious with sites that have migrated by progressive sections. If you submit all HTTP URLs while only 30% of the site is actually in HTTPS, you create a mismatch. In this case, it is better to submit in batches, syncing the HTTP sitemap with the actual progress of the migration.

What practical steps should be taken during an HTTPS migration?

Before the migration, prepare a comprehensive sitemap containing all currently indexed HTTP URLs. Use your Search Console data and logs to identify the URLs that are actually crawled by Google, not just your theoretical structure. Some outdated or soft 404 URLs do not need to be included.

On the day of the migration, submit this HTTP sitemap either via the old Search Console property (if it remains active) or via the new HTTPS property. The latter option is often more convenient as it centralizes everything on the new property. Check that the 301 redirects are in place before submitting; otherwise, you may lead Googlebot to errors.

How can you verify that the strategy is working?

In Search Console, monitor the index coverage report on the new HTTPS property. You should see a gradual increase in indexed HTTPS pages and a corresponding decrease in the old HTTP property (if you have kept it). This switch should be noticeable within 2-3 weeks for an average site.

Analyze your server logs to confirm that Googlebot is actively crawling the HTTP URLs and following the 301s. Look for requests with the user-agent Googlebot, HTTP status 301, then check that the bot is subsequently crawling the target HTTPS URLs. If you see many uncaught 301s, that's a warning signal.

What mistakes should be absolutely avoided?

Do not leave the HTTP sitemap in place indefinitely. After 6-8 weeks, remove it or replace it with the HTTPS sitemap. Maintaining both versions creates ambiguity and may slow down the complete consolidation of signals. Google will eventually understand, but you waste time.

Avoid submitting an HTTP sitemap containing non-critical URLs or duplicate content. If you had 10 variants of URLs for the same page (session parameters, tracking, etc.), submit only the canonical version. Otherwise, you waste crawl budget on redundant redirects.

• Prepare a comprehensive sitemap of indexed HTTP URLs before migration
• Verify that all 301 redirects are in place and functioning (manual testing + Screaming Frog crawl)
• Submit the HTTP sitemap via Search Console (old or new property)
• Monitor server logs to confirm the spike in Googlebot crawling within 48-72 hours
• Follow the Search Console coverage report to check the gradual increase in HTTPS indexing
• Remove the HTTP sitemap after 6-8 weeks, once the migration is consolidated