Fix: An Error Has Occurred Please Try Again – Google Webmaster

Fix: An Error Has Occurred Please Try Again – Google Webmaster

If you try to submit a new URL in Google Webmaster tools, you may receive a general error and to try again later.

 

An error has occurred. Please try again later.

 

More than likely, the error is specific to Google Webmaster tools. Some have reported the same sporadic error and the Google URL index queues may be backed up. However, some others suggest to try the following.





1. Submit a new URL using “FETCH” and not Fetch and Render.

Google webmaste tools fetch and render

 

Some have reported being able to get past the error occurred message this way. If you continue to experience the issue, use the comments form below and let us know. More than likely, others are also experiencing the same issues as is a Google issue.

* Please use the comment form below. Comments are moderated.*



Related Posts

 

Comments 7

Guest - jenous.net on Saturday, 02 February 2019 04:03

today i have this error in my google console

today i have this error in my google console
urzh on Saturday, 02 February 2019 06:38
Try using the new Console. https://search.google.com/search-console
Guest - Caroline on Thursday, 03 May 2018 18:23

Andre Satria, "Fetch & render" and then requesting they index the page and linked pages is best practice when doing an HTTPS migration, especially of large sites (in addition to a long list of other things which don't — or adding a new site, or changing your permalink structure. It's recommended to use that option particularly for top pages on the site. I've just completed an HTTPS migration for three sites, and am getting this error, which is slowing down the crawl rate for my sites. One of them has 3,000 posts, so this error is frustrating — and if it's quota related, the removal of the quota notification feature is not helpful.

Andre Satria, "Fetch & render" and then requesting they index the page and linked pages is best practice when doing an HTTPS migration, especially of large sites (in addition to a long list of other things which don't — or adding a new site, or changing your permalink structure. It's recommended to use that option particularly for top pages on the site. I've just completed an HTTPS migration for three sites, and am getting this error, which is slowing down the crawl rate for my sites. One of them has 3,000 posts, so this error is frustrating — and if it's quota related, the removal of the quota notification feature is not helpful.
Guest - andre satria on Friday, 23 March 2018 23:03

This is often a sign of getting close to useing up the quota. Alas the exact error message doesnt seem to survie though the system. Why are you trying to use 'request indexing' anyway?

This is often a sign of getting close to useing up the quota. Alas the exact error message doesnt seem to survie though the system. Why are you trying to use 'request indexing' anyway?
Guest - sandeep on Monday, 26 February 2018 10:35

I also have the same issue. however i also got ""Server connectivity error". more then 2 days have been passed, I am still suffering with this issue. However my site is working absolutely fine. I never had this issue before, just recently i installed "Engintron (Nginx) plugin to my WHM/Cpanel" and after 2 days this happened. is this happened because of this?

I also have the same issue. however i also got ""Server connectivity error". more then 2 days have been passed, I am still suffering with this issue. However my site is working absolutely fine. I never had this issue before, just recently i installed "Engintron (Nginx) plugin to my WHM/Cpanel" and after 2 days this happened. is this happened because of this?
Guest - kannan on Friday, 16 February 2018 04:00

Still it Displays like that. An error has occurred. Please try again later.

Still it Displays like that. An error has occurred. Please try again later.
Guest - Olivier Onorato on Thursday, 21 December 2017 13:03

Using "Fetch" only as suggested above does not fix the "An error has occurred. Please try again later" issue.
Also, I submitted 40,000 pages and only 600 got indexed. No reported error in my sitemap.xml file.
Any ideas?
Thanks

Using "Fetch" only as suggested above does not fix the "An error has occurred. Please try again later" issue. Also, I submitted 40,000 pages and only 600 got indexed. No reported error in my sitemap.xml file. Any ideas? Thanks
Friday, 29 March 2024