Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PracticeExampleWhyHow to Do It
Remove context root.http://bonsaiframework.com/content/bonsai/index.html http://www.bonsaiframework.com/index.html The context root is not relevant to customers....




Normalize to www

http://bonsaiframework.com http://www.bonsaiframework.com

Including full urls such as http://bonsaiframework.com/ubuntu/http://www.bonsaiframework.com/ubuntu/

Visually it's more appealing and ensures your domain name stands out more.Bonsai Framework show how to enforce www but for large organizations consider working with your CDN.
Do not requires index.html.http://www.bonsaiframework.com/ubuntu/index.html http://www.bonsaiframework.com/ubunut/ Visually more appealing and less work for users.

Baked into default by Apache but you need to build your site using index.html files and not something like http://www.bonsaiframework.com/ubuntu/homepage.html as our starting page.

For organizational search engine optimization reasons you may need to use special names. In that case ... (I gotta review the best method still here).

File names versus folders.

Folder approach.

http://www.bonsaiframework.com/ubunut/
h
ttp://www.bonsaiframework.com/ubuntu/setup/

File approach

http://www.bonsaiframework.com/ubunut/ubuntu.html
http://www.bonsaiframework.com/ubuntu/setup.html

The argument for folder based approach is it looks more visually appealing.

In the folder approach you need to create folders and the file name itself is called index.thml.

File approach is self explanatory.





Use Sub Domains

www.linux.bonsaiframework.com www.bonsaiframework.com/linux

However, there are arguable cases (fast type for often used distinct sub-site or restrictions (ie separate system).

www.bonsaiframework.com - public site
www.wiki.bonsaiframework.com - secure site used for authoring internal content.







Internationalization and urls

There are 3 popular variations, often with the home country being the .com. In this case I'm Canadian,

Subdirectory

www.bonsaiframework.com/ca/en - Canada English
www.bonsaiframework.com/ca/fr - Canada French
www.bonsaiframework.com/mx/es - Mexico Spanish

Subdomain

www.bonsaiframework.com.com/en - Canada English
www.bonsaiframework.com.com/fr - Canada French
www.bonsaiframework.com.mx/es - Mexico Spanish

www.bonsaiframework.com/en - Canada English
www.bonsaiframework.com/fr - Canada French
www.mexico.bonsaiframework.com/es - Mexico Spanish

Not sure there is a best one here so will discuss some pros and cons.

Subdirectory


Subdomain

Advantage - possible to bind to different systems for ease of migration (say moving to a new CMS one site at a time).

Disadvantage - there are some ssl certificates overhead to maintain with more subdomains. Adam chime in here if modern certs make this overhead negligible.


ISO letter country code followed by ISO letter language code.

For country code, use the 2 letter SO 3166-1 alpha-2 supplemented by three-letter ISO 3166-1 alpha-3 codes when no two-letter code is applicable.

Similarly for language code, use the 2 letter ISO 639‑1supplemented by three-letter ISO 639‑2 codes.





Canonicalize your duplicate pages....





Switch to SSL TLS version current down to 1.1 or for marketing consider 1.0.www.bonsaiframework.com https://www.bonsaiframework.com

Better rankings in search engines and confidence in users. Additionally prevents alleviates against man-in-the-middle attacks.

Any collection of customer information should use TLS 1.2 or higher.

Redirect is straightforward.

The challenge for large organizations is how to redirect for older browsers that simply do not support the minimal TLS (this needs to be it's own article).

Today (Oct 2017) google still supports TLS 1.0. The PCI Council originally wanted to declare TLS 1.0 obsolete by June 30, 2016 but since pushed back to June 30, 2018.

Put here how older browsers will react to a large search engine that has dropped tls 1.0.





Redirects should be file based and generally aim to use 301 "Moved Permanently".

Moved permanently is best for SEO and passes between 90-99% of ranking power to the new page.

Note transferring content becomes more complex when an entire site changes its domain or when content moves from one domain to another. 

If you have a CDN look for an API which under the hoods uses a web server redirect.

For example Akamai's Edge Redirector Cloudlet can be programmatically populated via their API.

You may use your Web Server such as Apache mod_rewrite with the caveates,

  • Lose the speed of rewrites happening on the CDN edge servers.
  • May create significant load on your Web Servers.