Pete, Mine is https with a valid letsencrypt. They will not index.
Sent from my iPhone
On May 7, 2019, at 10:25, pete M petem001@hotmail.com wrote:
If I am not crazy. Google wont index new web site if not https.
Télécharger Outlook pour Androidhttps://aka.ms/ghei36
From: 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org on behalf of Rob Janssen pe1chl@amsat.org Sent: Tuesday, May 7, 2019 12:10:52 PM To: 44net@mailman.ampr.org Subject: Re: [44net] Google indexing
Rob, Sorry, I forgot to say which site: separs.ampr.org http://separs.ampr.org/. Yes, there are indexed ampr.org http://ampr.org/ subdomains, but I don’t seem to be getting my point access. Those domains are older and indexing no longer works.
You can keep iterating that, but it is simply not true. You undoubtedly have difficulties and I'm sure they are difficult to solve, but they aren't ampr.org wide.
Eventually according to Google, they will fall off their indexing. Google indexing can no longer reach them or any new site.
Maybe your friend has told you that, but he has told you other things that are wrong. So I would not count on that.
- I asked Brian to add a TXT entry, as per the Google Search console instructions.
It is in fact not required to do that, you can create a textfile with a name that is the same as what you put in the TXT record and it will work the same way. I have added sites to the search console in the past and used that method, it worked fine.
- Initialy Brian did not want to do it, saying he didn’t want Google crawling all the 44net IPs
Contrary to what some "researchers" (and some of our fellow amateur radio operators) enjoy doing, Google is not portscanning the IP space to find sites to crawl. Google indexes HTTP links and follows them. Of course this takes bandwidth, but that is not much when compared to the many many black-hat and white-hat portscanners.
9)I attempted to have the Google Search Console crawl the site. It declined indicating "no errors" but an “anomaly”
I cannot help you with that. Your site appears OK from the outside, and my site(s) are indexed just fine. There is only one thing I cannot check: there could be some firewall filter that drops Google indexing (usually from 66.249.64.0/19) in the ampr gateway or in another system in the path to you. (our local sites within 44.137.0.0/16 are not routed via that gateway so we are not subject to that filter if it exists)
However I don't think that is the case because there are other sites that are being indexed.
Rob
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Roger,
May I suggest looking at your web site home page load / rendering performance? I tried loading your page in the Google Page speed Insights https://developers.google.com/speed/pagespeed/insights/ tool. It will not complete loading your URL for analysis, returning the much too common NO_FCP error message. (see their tool's references for details on FCP. I was able to load your URL in the analyze.websiteoptimization.com tool, which shows the page is almost 3MB in size, mostly images and javascript, which may be slowing the page load/rendering. While 3MB may not seem all that much in today's fast networks, home page size and load times have been known to cause crawling index systems to skip the site due their limited budget in time and resources. Poor performance scripting can be an issue too. If your network route to users, or in this case analysis tool, crosses a slower network gateway, the size of your page and content rendering performance could have even more impact. Don't know if improving page performance will make Google indexing happier, but can't hurt to try.
At one time I had access to better tools for web site analysis, but I've retired, so I no longer get to play with that stuff.
Regards, David M. WD5M
-
David McAnally -
Roger