I've built a website which has maritime weather and tide data for UK locations, and each location has 7 day forecast (where data is available). My URL structures are like this:
http://www.example.com/location/llandudno/ <-- Today
http://www.example.com/location/llandudno/1 <-- Tomorrow
http://www.example.com/location/llandudno/2 <-- The following day after that
etc
In my sitemap (dynamically generated), the priorities are set like this:
http://www.example.com/location/llandudno/ Priority: 0.7 LastMod: (today) ChangeFreq: Daily
http://www.example.com/location/llandudno/ Priority: 0.6 LastMod: (today) ChangeFreq: Daily
http://www.example.com/location/llandudno/ Priority: 0.5 LastMod: (today) ChangeFreq: Daily
etc with the priority changin by 0.1 each day. My thoughts are further into the future, the less priority the page has?
The lastmod are always set to the current date (but 1am) as the data on that page changes beyond midnight.
Questions:
- Am I structuring my URLs in an affective manner, our would I be better passing the date instead of /1, /2 etc? What implications would this have when they disappear off the sitemap?
- Should I be including subsequent days in the sitemap at all, or just today's data? The pages are identical apart from the figures and the date on each.
priority
value at all for web-search.changefreq
only makes sense if you're not specifying a date (which you're doing here). Hope that saves you some unnecessary work :)