Ranking Again Drop After redirect domain Please Guide me

[raagjattmusic]

The ranking of my website had gone down when Google core update started, after 20 days I changed the extension of the domain and put a 301 redirect on the new domain. all my keywords were recovered and the traffic was also the same as before. But after 1 month today again Google dropped the ranking, what should I do?

 

[GeeLark AI]

if the same thing happens, could be from your on-page or related to your site loading speed

 

[SEO Sparton]

The ranking of my website had gone down when Google core update started, after 20 days I changed the extension of the domain and put a 301 redirect on the new domain. all my keywords were recovered and the traffic was also the same as before. But after 1 month today again Google dropped the ranking, what should I do?

continuously monitor for the algorithm update and be ready to make necessary changes to your SEO plan according to it. asses your website content quality and relevancy. also consult any SEO analyst for more assistance.

 

[NeedMyLink]

Check your 301s for errors, and give it time. Keep an eye on Google Search Console for any issues, and maintain your focus on top-notch content. Rankings should stabilize eventually.

 

[bobblack225]

Check to see if your site has any seo errors or optimization errors.

 

[Starblazer]

It's mostly because of on-page SEO. Check your website pagespeed insights and see if you need to improve anything.

 

[tonoufriqueunno5056]

Most likely, your SEO is having errors.

 

[RogueDreamer]

Check you seo and gsc regularly to avoid these kind of issue. Make some changes in quality of the content

 

[Monsterer]

Hi @raagjattmusic

may I know why you redirected after the update and what is your niche?

First, you have to wait for the algorithms to fully roll on after that you again work on the rankings and traffic for the main domain

As the last step you have to do the redirection

 

[blackbeans]

You might want to monitor the progress of your traffic over the coming weeks.

It may well turn out that it's not the 301 redirect but part of the larger core update that caused your problems.