I still think the difference between
http://www.ctwug.za.net
&
http://ctwug.za.net
should be pointed to the same CNAME / A record
further more also get a “.co.za” domain, since Anything.za.net falls under one .za.net domain for SEO / indexing.
i.e. google thinks any domain listed in the .za.net space is 1x domain and see them all as sub domains for .za.net.
Split this off as it’s a separate topic as it was off topic there:
The ctwug.za.net needs to point to the wiki as ctwug.za.net/radioname needs to point to a wiki page for that radio to allow people to find the highsite from the SSID. See our naming convention for details.
This is hosted on a separate machine. I might do a redirect for the root folder of that site once I get our landing page up from ctwug.za.net to www.ctwug.za.net (which will become the landing page).
This is incorrect. za.net is listed as a public suffix, meaning subsites of za.net should be considered separate sites by people using the public suffix list. Not sure what Google Search specifically does. I know many browsers use that list (including Chrome).
You can see it here. It’s the very last entry.
// ZaNiC : http://www.za.net/
// Submitted by registry <hostmaster@nic.za.net>
za.net
za.org
As far as I know that should signal that subdomains to that site should be considered separate sites.
We do have both co.za and za.net though we don’t use co.za much. Essentially we have a backup plan if za.net goes away at some point. We could start moving to that sooner as well. I have considered making the domains the same at least. E.g. mypc.mynode.ctwug.za.net and mypc.mynode.ctwug.co.za becomes the same. Haven’t gone there yet as it’s a bit of potayto vs potahto.
We’ve not done much in terms of SEO optimisation. I don’t have feelings in terms of wether it should be priority. I feel that our internal network issues should have higher priority though.