It looks like I installed the plugin sometime before July 12, and the link in the first notification that I received on July 12 worked. Nothing worked after that. That’s about the time I started trying to fix links not working.
I’ll just run through what I did, and you might be able to see how I tripped up the plugin.
I originally built the site years ago as HTML with no SSL certificate. There was a second domain name pointed at the site through my host. Still is. I paid no attention to the site.
I rebuilt the site this year as a WordPress site and changed it to https://
I did a lot of Googling to see what pages were ranking and was surprised to see the old parked domain URLs were showing up everywhere, but not the old real domain URLs. Still not sure why. And all the old parked URLs without the https in search pages were throwing 404 errors.
I installed your plugin and the SEO Redirection plugin and over many days redirected old URLs with the real domain to changed URLs on the new site. And then I redirected all the old URLs from the parked domain to the new site, though that felt like overkill, but it made the links work in search pages.
I’ll give examples.
Real domain: https://mysite.com
Parked domain: https://mysitetoo.com
Every URL with https://mysite.com/something was redirected to https://mysite.com/replacementpage.
And every URL with https://mysitetoo.com/something was redirected to https://mysite.com/replacementpage.
Upon investigation just now, I’m seeing that I redirected https://mysitetoo.com to https://mysite.com.
My question to you is: If I redirected the parked site to the new site through the SEO Redirection plugin and the host also is forwarding the parked domain to the new domain, have I accomplished what you just described I might have done?
I should remove the redirected entry for https://mysitetoo.com. I didn’t give it a thought when I did it, but it does seem like a poor choice due to the redundancy.
I really appreciate you investigating this. Hopefully, my error will save others from creating the same issue.