This Site Inventory Tool will create a report showing all content on your current site. To help navigate the tool we put together Content Report Resources to explain what each part of the spreadsheet needs and how to deliver it to your team. Use this report to:
- Determine the content that will be migrated to the new site.
- Cross reference with analytics to determine which pages performed and which ones didn't. This will be a big help in the content strategy process.
- Review your content for calls to action.
- Refine and edit content so that calls to action are compelling and clear.
- It would be wise to include notes on placement (sidebar, blockquote, etc.) that will help migrators know what content goes where on a page and how it should be displayed.
- Create a page tree for all content.
- Migrators will use this as a guide to build the folder structure as well as create accurate page links in content for pages that have not been created yet.
- If using the content from an old site, the migrators will use the spreadsheet to know 1) where the content was and 2) where the content needs to be on the new site if the location has changed.
- Add new pages and/or update folder structure
- With the limitation of six main navigation items, there could be cause to regroup content under different headings or create new headings that have a broader scope.
- Reference redirects and give migrators direction to where content is
- Keep track of where pages were on the old site and where they will be on the new site. This will make building the content for the redirects simple and quick even if you have several pages that need a redirect.
- Assign categories to content that will need relationships.
- Service content will need categories assigned to each service before the host can be built. Other content will use these categories to create relationships throughout the site (eg. building content, physician content, new items, etc.). We have documentation on how to choose categories for services as well as items needed before building the host in dotCMS.