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.
Eventually according to Google, they will fall off their indexing. Google indexing can no
longer reach them or any new site. It doesn’t matter if you have links, Google can’t index
ampr.org <http://ampr.org/> subdomains so when it follows thew link, it’ll fail to
index. And here is how I know that:
1) I created the Gateway.
2) I created the website
separs.ampr.org <http://separs.ampr.org/>
3) I logged into the “Google Search Console”
4) I could not have Google verify site ownership. It seemed block to them.
5) I asked Brian to add a TXT entry, as per the Google Search console instructions.
6) Initialy Brian did not want to do it, saying he didn’t want Google crawling all the
44net IPs
7)I assured him that it was only for site verification and they would only crawl my site.
8) he agreed and through the Google Search Console I had the site ownership Verified.
9)I attempted to have the Google Search Console crawl the site. It declined indicating
"no errors" but an “anomaly”
10) I tried quite a few times:
a) as the site is now (declined “anomoly”).
b) I tried with deleted my robots file. (declined “anomoly”)
c) I tried by removing everything in my public_html directory and added only a file
index.html file (declined “anomaly”)
11) I added a sitemap.xml to the search console (and the Google Search Console downloaded
it. It then said it would not index because of an “anomoly” .
12) The Google Search Console will not index and always says it is due to an “anomoly” It
makes it clear it is "not an error". The site is accessible, but an “anomoly”
stops the index.
13) This is where I contacted "my friend” (more of an associate rally) and I asked
her what an “anomoly” would be. She checked and said the “anomoly” is related to either
DNS, Meta header, or robots.txt in the TDL (
ampr.org <http://ampr.org/>) preventing
Google from indexing. She made it clear that Google tries very hard to honor any setting
that suggests the site does not want indexing. So that’t where the “friend” comes into
play. I’m sure you all know that under normal circumstances there is no possibility to
contact Google. I was fortunate I had someone I could ask. I’d hoped her information would
help sort this out.
14) She also advised me that a quick look at
ampr.org <http://ampr.org/> subdomains
that have been indexed (those that you’ve suggested prove indexing works) are well over 1
year old (usually 2 or more.) Those sites will not be reindexed as things stand today,
unless the “anomoly” is corrected. New sites will not be indexed - ever! (unless something
changes and regardless of how many links you have on other sites) I couldn’t get her to
tell me exactly what the problem is because I don’t own
ampr.org <http://ampr.org/>.
Probably because she is only an associate that I met twice and doesn’t really know me
that well. I don’t own
ampr.org <http://ampr.org/> after all.
So I’m hoping this clarified the issue.
Please add your own site to the search console and see what I mean. If you can get it to
index, then I’d like to know what is different between yours and mine.
73
Roger
VA7LBB
On May 6, 2019, at 12:00 PM,
44net-request(a)mailman.ampr.org wrote:
Send 44Net mailing list submissions to
44net(a)mailman.ampr.org
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.ampr.org/mailman/listinfo/44net
or, via email, send a message with subject or body 'help' to
44net-request(a)mailman.ampr.org
You can reach the person managing the list at
44net-owner(a)mailman.ampr.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of 44Net digest..."
Today's Topics:
1. Re: Google indexing (Rob Janssen)
2. Re: 44Net VPN? (Heikki Hannikainen)
3. Google indexing (lleachii)
From: Rob Janssen <pe1chl(a)amsat.org>
Subject: Re: [44net] Google indexing
Date: May 6, 2019 at 2:27:24 AM PDT
To: "44net(a)mailman.ampr.org" <44net(a)mailman.ampr.org>
When one asked what your site was, you didn't
reply. If it's
va7llb.ampr.org,
it is unreachable from the internet today. That'd stop more than Google
indexer...
As we still did not get that information, I checked the DNS zone and there are only two
TXT records for google site verification. One is for
va4wan.ampr.org and their site is
indexed by Google, no problem there. You can lookup
site:va4wan.ampr.org to confirm
that.
(again: the "site:" in that is important, don't omit it)
The other is for
separs.ampr.org and Google does not yet know about them.
So probably he is discussing that. It appears to work OK when visited inside and
outside
of AMPRnet and its robots.txt also appears OK.
I think it is just external linking that is required. Try to get a link to your site
from
the city website where it had an information page before. Make links from your local
club, from private sites of your members, etc. Then Google becomes more convinced that
this is a useful site that people may want to visit, rather than some scam that wants to
have quick visitors and then disappear. (of which they probably get thousands a day
submitted)
And of course you need patience. It will not happen overnight.
We all know that it is difficult to communicate with them and that they do what they
themselves
consider appropriate. You will have to live with that, we all do.
Rob
From: Heikki Hannikainen <hessu(a)hes.iki.fi>
Subject: Re: [44net] 44Net VPN?
Date: May 6, 2019 at 3:09:50 AM PDT
To: AMPRNet working group <44net(a)mailman.ampr.org>
On Tue, 30 Apr 2019, KJ7DMC wrote:
Hello,
This is sort of a follow up to my last email, which I ended up figuring
out. This link,
http://he.fi/amprnet-vpn/amprnet-vpn-win.zip to download
the amprnet crt file is invalid. Any idea where I would obtain that file
from?
Hi,
The download links for the VPN config files work again now. Sorry for the website outage;
server migration taking a bit longer than expected due to Real Life Events (TM). :)
The included certificates are signed with weaker-than-desired hash algorithms, and modern
TLS/VPN software are beginning to reject them. I suppose I'll have to make new ones
soon and publish new config files along with them. The security issue is not that huge on
AMPRnet use, but it'd be nice if it worked out of the box.
- Hessu
From: lleachii <lleachii(a)aol.com>
Subject: Google indexing
Date: May 6, 2019 at 11:45:48 AM PDT
To: 44net(a)mailman.ampr.org
All,Don't these sites all appear to be indexed in the past?73,- LynwoodKB3VWG
null
_______________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net