Signed up for Google Search Console to check if they can index my website properly.
I have a blog post that was active on my previous blog on the same domain. I set up a redirect to ensure the link to it is still working (so redirecting from a clean URL to the actual Micro.blog address). And now I have this error message.
Is there any way to fix it with Micro.blog?
In Search Console, which two pages are listed as duplicates?
I have a link https://molodtsov.net/formula-1
that redirects to https://molodtsov.net/2022/07/16/formula.html
using the in-built redirect feature.
Google Search Console lists the second link as the issue.
Tried to manually validate the fix, but it persists.
Technically, there’s more than one way to set up a redirect. In this case, it’s a 302 Found which indicates a temporary redirect.
Google sees temporary redirects as a weak signal that its index should be updated. In other words: Google might ignore the redirect and keep the old page in the index. When I write this, that seems to be the case, the old URL is still in Google’s index.
You could try manually removing the old URL from the index, that might get rid of the issue.
That’s interesting. We could change our redirects to a “301 permanent” redirect, but I’m not sure that will always be right either. Might need to be a setting.
Will try this, I suppose Google could still have an index of my previous blog structure.
I would really like a setting for this. It would help a lot to get things settled down post-WordPress migration. I would also settle for some sort of config setting that let me specify my redirects as permanent, but I don’t know if something like that even makes sense from the coding side of things. I could try uploading bulk uploads to Cloudflare, but my impression is that Cloudflare and Micro.blog don’t always play well together. Also: your redirects take effect right away, which is nice.
It would be great if there was a setting to create a 301 or 302 redirect, but apart from the manually created redirects, I think that in any case the redirect from the www tto the non-www version of your site should be 301. According to Redirect Checker, https://www.example.com to https://example.com is currently also a 302 redirect.
