A good sitemap is a functional web-design tool that allows to administrators to easily see the structure of website, along with an overview of it’s content. A sitemap can be useful for quickly bringing a new admin up to speed on a site, quickly reviewing navigation and structure, and determining what content should be on a site in case of a failure or restoration from a backup.
There are two different types of sitemaps—one used for Search Engine Optimization (SEO), meant to be parsed by a computer, and a visual sitemap, meant to be used by human beings. Since eLearning is less concerned with how Google indexes our sites (the majority of our traffic is internal), this project will focus on creating a visual sitemap for LCC eLearning Admins.
A separate sitemap will be created for each eLearning site (Instructor and Student). These sitemaps will include:
The title of each currently visible page, nested under the category(s) it appears on on the website
A list of links on each page
A brief summary of any other content on the page
Date that page was last updated, and by whom
What are best practices for generating and maintaining a sitemap? Can it be automated?
Is there key information that a sitemap should contain other than what is outlined above?
The Wordpress Sitemap Plugin has been deployed on both /stest and /itest. Given the database parity between the two sites, it’s not necessary to reply the sitemaps to production—they will be updated with an semi-annual refresh of the test instance database. URLs for sitemaps are: