Pescao6

It could be your robots.txt although you would need to clear the system caches and if applicable the CDN cache as well before testing Try the recommended robots.txt

Those new AI bots are impressive for lack of a better word.

These dates are from GoDaddy Website Security Basic which is a feature from having a GoDaddy Domain with Ultimate Protection ($30/yr). I just called GoDaddy because I noticed they have new products... GoDaddy Website Security = Sucuri GoDaddy Website Security Basic = Sucuri Monitoring GoDaddy Website Security Standard (formerly GoDaddy Website Security Deluxe) = Sucuri Pro

This is interesting... US Partial Outage was recognized and they're doing maintenance since an hour ago expected to end Tomorrow at 15:00 EDT. This is from Uptime.com which doesn't appear to have detected the few seconds/minutes of downtime.

Yes, but 20% of AWS is between the United States and Canada. If you have latency with your connection between Europe and the United States, you can use a VPN to redirect your connection allowing you to have a faster stable connection. Basically what can happen is that there might not a problem with your ISP and there might not be a problem with the Web Host but there could be a problem somewhere in between where the internet connects your ISP to your Web Host. My website has only gone offline on Aug 26; it was down for 30 minutes because the Data Center where I'm hosting went offline. Some recent dates of downtime detected have been: Jul 22, 31 Aug 1, 5, 6, 7, 8, 9, 13, 14, 15, 16, 17, 20, 29, 31 Sep 2, 6, 17, 18, 20, 26, 27, 29, 30 Oct 3, 4, 5, 8, 9, 11, 12, 14 These probably lasted a few seconds/minutes or using Cloudflare CDN kept my website online.

Cogent Communications had several outages in the United States. There is not much Amazon could've done. I recommend using a VPN with a location anywhere outside of the United States if you're still having slowness.

Try using a VPN; there have been several internet outages for the last few weeks. If you can connect with a VPN, call your ISP. If you can't connect with a VPN, contact your Web Host. You can also use Command Prompt (cmd) and run a trace route to see if you can spot where the connection is dropping: tracert forum.evasionmoto34.com Your Web Host's Data Center in France (51.83.70.184) is experiencing high latency and the Data Center in Canada (192.99.146.68) has a network outage. Using Cloudflare as a CDN is free and might help in moments like this.

I experienced the same thing here.

I would recommend that you: Go to AdminCP -> System -> Site Promotion -> Search Engine Optimization -> Friendly URLs a) Enable Friendly URLs b) Rewrite URLs c) Force Friendly URLs Go to AdminCP -> System -> Site Promotion -> Search Engine Optimization -> Sitemap -> Use recommended settings Go to AdminCP -> System -> Site Promotion -> Search Engine Optimization -> Crawl Management -> Invision Community Optimized Download the robots.txt and upload it Then go to AdminCP -> System -> Support -> Get Support -> Clear System Caches If you're using a CDN, clear the CDN Cache as well Go to Bing and Google Webmaster Tools a) Resubmit your Sitemap b) Resubmit your home page URL The main things that should affect your SEO are: The quality of your content and the amount of content you publish. You can check on Google Trends for ideas. Give it 24-72 hours and you should see your ranking change. I saw ranking changes within a few hours after applying changes. You can hire low quality text writers for $5 on Fiverr. I am convinced that what I know is bad SEO is also great for SEO.

When we had v3, a lot of people used WordPress as a homepage and then had Invision Community Forums at /forums/ But the whole point of v4 was to make a better website suite so you could have all of the features on the same platform v5 should be fine because we'll be able to re-arrange the content better If you put 300+ words on the home page, you're good This gave me some 2007-2010 vibes when I had a table as an announcement box with scrollable text SEO still matters: I'm still fixing my ranking on Google.com after I wrote a To Do for myself which could be considered a guide for others, but I'm ranking #1 on Google Gemini Links don't break if you switch the default application from Forums to Pages. If you hosted Invision Community on public_html and your Forums were on domain.com, going to domain.com/forums/ would've opened the Forums so nothing changes. If you make a /home/ page, then domain.com and domain.com/home/ would also take you to the same place. If you're saying that you made a public_html/forums/ subdirectory or had a previous forum on a subdirectory like public_html/community/, you could use Friendly URLs or .htaccess to redirect everything. 301 Permanent Redirects don't have a negative impact on SEO; 404 errors due to lack of redirects is what could temporarily have a negative impact your SEO.

AdminCP -> System -> Settings -> Advanced Configuration -> Security -> Trust IP addresses provided by proxies?

With major website changes including updates and changing images, you may need to clear the ACP cache, Cloudflare CDN cache, and your web browser's cookies and cache files. Purging a CDN cache can take a few seconds, and certain applications may also temporarily cache your site which might take a few minutes for them to automatically clear. If you're testing changes, it could be a good idea to temporarily toggle Cloudflare's Development Mode to Temporarily bypass the CDN cache under Caching -> Overview -> Quick Actions.

I had a similar problem with RSS exports while using StackPath fixed with this exception:

If you use a CDN, make sure to also clear the CDN cache. PS: After major website changes, you may need to clear your web browser's cookies and cache files.

The only thing I would add to what others have already mentioned is to backup the entire website using JetBackup or something like it before you upload the new Invision Community 4.7.18 files. But for the most part, manual upgrades work as well as new installations. If it breaks, you could always try to reupload/override the files and repeat the /admin/upgrade process. Worst case scenario, you could always restore the website from a backup.