Hello,
Thank you for contacting Rank Math and bringing your concern to our attention. I’m sorry for any inconvenience this issue may have caused you.
I’ve checked your site, and it seems that it’s already appearing on the Google search results page. Please see the attached screenshot in the designated Sensitive Data section.
I hope that helps. Thank you, and please don’t hesitate to contact us if you need further assistance.
Thank you for the reply.
Yes, but your search was not done with “mirisna” which is a key word.
My site was ranked first in Google just by using a key word, and bellow the site title were listed pages.
Now they are listed as separate pages – as if there is no site to keep them togerher..
Also, when you enter just “mirisna” is shows about page – no home page:-(
That’s what happened the last time, before i disabled instant indexing and asked google to recrawl my site.
Now I’ve rolled back to the versin before this 71 (the two latest updates) and asked Google to recrawl again…
Can you explain why the key word totally misses site’s homepage, after your updates?
Thank you
Hello,
Your site seems to show up with the keyword from my end, check the screenshot I added in the sensitive section.
That said, Ranking on Google can change for several factors and no one (except Google) can control them.
It can be just a temporal ranking change due to some algorithm update so you could have your rankings back soon or you could need to optimize the content and do some off-site SEO optimization.
Hope that helps and please do not hesitate to let us know if you need our assistance with anything else.
Thank you for the reply. The Google search results are back because I rolled back to the version 1.0.56.1. and Google recrawled it.
After the versions 1.0.57.0 and 1.0.57.2 were active I could not even submitt a request from Google Search Console to index the site.
Nothing else was changed in the mean time.
Just letting you know – staying on the previous version for a while.
You may close the ticket.
Hello,
Thank you for the update.
It seems that it’s already working for you after rolling back to version 1.0.56.1 and resolved the issue.
If you have any other concerns, please don’t hesitate to contact us anytime by creating a new ticket to assist you further with anything else.
Thank you.
