You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Best practice for SEO says to use subfolders rather than subdomains, but for CC historically, subdomains have been a method of organizing the site (see: search.creativecommons.org, ccsearch.creativecommons.org, network.creativecommons.org, etc.)
"Search engines keep different metrics for domains than they do for subdomains, so even though Google itself has stated that — from a ranking perspective — content in subdomains and subdirectories is treated roughly equally, it's still recommended that webmasters place link-worthy content like blogs in subfolders rather than subdomains (i.e. www.example.com/blog/ rather than blog.example.com)."
Because we don't have competitors in the space or similarly named organizations, I think we should be fine, but I don't want to muck up our search rankings by creating a bunch of subdomains or maintaining historical subdomains for no reason.
This is particularly important because of the new network sites coming online. For this reason, I am tagging @robinpuga@robmyers@ericsteuer@pa-w
The text was updated successfully, but these errors were encountered:
We currently only use subdomains for different sites (ex. blog.creativecommons.org redirects to creativecommons.org/blog/). I am not aware of any plans to combine sites (with the exception of moving the chooser from beta-chooser.creativecommons.org back to creativecommons.org/choose).
Best practice for SEO says to use subfolders rather than subdomains, but for CC historically, subdomains have been a method of organizing the site (see: search.creativecommons.org, ccsearch.creativecommons.org, network.creativecommons.org, etc.)
"Search engines keep different metrics for domains than they do for subdomains, so even though Google itself has stated that — from a ranking perspective — content in subdomains and subdirectories is treated roughly equally, it's still recommended that webmasters place link-worthy content like blogs in subfolders rather than subdomains (i.e. www.example.com/blog/ rather than blog.example.com)."
Because we don't have competitors in the space or similarly named organizations, I think we should be fine, but I don't want to muck up our search rankings by creating a bunch of subdomains or maintaining historical subdomains for no reason.
This is particularly important because of the new network sites coming online. For this reason, I am tagging @robinpuga @robmyers @ericsteuer @pa-w
The text was updated successfully, but these errors were encountered: