[Please Help] Google Search Console Errors Solve

MF Group

Senior Member
Jr. VIP
Joined
Mar 5, 2024
Messages
929
Reaction score
159
I have a website recently I transferred it from old domain to new domain. After that I am seeing that my new pages are indexed but old pages are shown 301 redirect error in GSC. How can I solve this problem? If I delete old pages from GSC will it harmful for me new website. Thanks
 
you should chill for a bit because google's kinda slow with this. It takes a while for it to catch up that you’ve moved your old pages showing as redirects is pretty normal at the start. double check your redirects make sure every old page properly points to its new home. If something’s off, it might mess things up. dont rush to delete old pages from GSC It doesn’t really help and might confuse things more. those redirects are supposed to tell goofle where the party has moved to.

Thanks!
 
@DXB nailed it right. However, I have heard some Googlers say that you need to declare the new domain urls using cross domain rel canonical syntax in the sitemap of the old domain.
 
@DXB nailed it right. However, I have heard some Googlers say that you need to declare the new domain urls using cross domain rel canonical syntax in the sitemap of the old domain.
When you've moved to a new domain, using the rel="canonical" link element across domains can indeed be a tactic to help search engines understand where the preferred content now resides. It's a bit like saying, "DXB, this thread used to live here, but now it's over there, and that's the version I want you to consider the original." But here the deal, though: adding those to your sitemap can be a bit tricky since sitemaps are generally used to list URLs you want search engines to crawl and index. But if you're in a situation where your old domain's content is identical to your new domain's, and you're using 301 redirects as well, adding rel="canonical" links directly on your old domain's pages to point to the new domain can reinforce the signal that the new domain is the preferred location for this content.

However, the advice you've heard about putting cross-domain rel="canonical" links in the old domain's sitemap isn't standard practice or necessary. The primary tools to signal the move to a new domain are 301 redirects and updating your sitemap on the new domain to reflect the current URLs of your content. Make sure you're also updating any internal and external links to point to the new domain as much as possible.

Hope you got it.

Thanks!
 
When you've moved to a new domain, using the rel="canonical" link element across domains can indeed be a tactic to help search engines understand where the preferred content now resides. It's a bit like saying, "DXB, this thread used to live here, but now it's over there, and that's the version I want you to consider the original." But here the deal, though: adding those to your sitemap can be a bit tricky since sitemaps are generally used to list URLs you want search engines to crawl and index. But if you're in a situation where your old domain's content is identical to your new domain's, and you're using 301 redirects as well, adding rel="canonical" links directly on your old domain's pages to point to the new domain can reinforce the signal that the new domain is the preferred location for this content.

However, the advice you've heard about putting cross-domain rel="canonical" links in the old domain's sitemap isn't standard practice or necessary. The primary tools to signal the move to a new domain are 301 redirects and updating your sitemap on the new domain to reflect the current URLs of your content. Make sure you're also updating any internal and external links to point to the new domain as much as possible.

Hope you got it.

Thanks!
I agree that's cross domain canonical element in the sitemap is unnecessary but it could fasten the process.

OP, If you need the code for the urlset canonicalization, let me know.
 
@DXB Nice explanation. Thanks
 
Y
I agree that's cross domain canonical element in the sitemap is unnecessary but it could fasten the process.

OP, If you need the code for the urlset canonicalization, let me know.
Yes I need
 
Alright, check it below.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>http://www.yourdomain.com/page1.html</loc> <link rel="canonical" href="http://www.otherdomain.com/page1.html" /> </url> </url set>
 
Alright, check it below.

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>http://www.yourdomain.com/page1.html</loc> <link rel="canonical" href="http://www.otherdomain.com/page1.html" /> </url> </url set>
Thanks a lot!
 
Slight correction.

Link tag is invalid in the sitemap protocol, so use this;

<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"> <url> <loc>https://olddomain.com/</loc> <xhtml:link rel="canonical" href="https://newdomain.com/"/> </url> <!-- Add more URLs as needed --> </urlset>

You might to hire a PHP developer to automate the sitemap generation for all pages on your site because you can't do it manually.
 
Slight correction.

Link tag is invalid in the sitemap protocol, so use this;

<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"> <url> <loc>https://olddomain.com/</loc> <xhtml:link rel="canonical" href="https://newdomain.com/"/> </url> <!-- Add more URLs as needed --> </urlset>

You might to hire a PHP developer to automate the sitemap generation for all pages on your site because you can't do it manually.
Sure. You are very helpful.
 
Back
Top