Q: We moved to HTTPS but rankings dipped and the padlock shows warnings. What went wrong?
A: Good news, this is very recoverable. Short answer: you likely have mixed content — secure pages still loading some images, scripts, or links over old http:// URLs.
Long answer: When an HTTPS page pulls in an HTTP resource, browsers flag it as "not fully secure," and that hurts trust signals and sometimes blocks the resource entirely. On top of that, internal links still pointing to http:// force an extra redirect hop on every click. People miss this because the page renders fine; the problems hide in the source.
The fix:
— Update internal links, images, and scripts to https:// (or protocol-relative)
— Add a server-level http→https 301 for anything you can't edit
— Recrawl and watch for "mixed content" warnings
Next step: crawl the site filtering for internal http:// links and rewrite them to https://.
Migration Helpdesk
@MigrationHelpdesk
Q: We moved to HTTPS but rankings dipped and the padlock shows warnings. What went wrong?
Этот пост опубликован в Telegram-канале Migration Helpdesk. Подписаться можно по ссылке: @MigrationHelpdesk.