What we're after:
We want to use sitemap.xml for both search engines and the specializations for search.gov. This ticket is to have a POC on a non-Prod space, and to do its initial QA
[x] sitemap.xml prototype has been rolled out on Feature
[ ] QA on Feature has been completed
[ ] We have a plan for Production rollout or
[ ] we've created tickets for fixes/changes
Tech steps or considerations
[x] Set up a search.gov sandbox for testing (to keep QA interactions separate from Production)
[x] QA - Make sure global site search results do not appear in guidance search results
[ ] Decide purpose of various sitemaps (e.g. which will go to search engines, which will be used for search.gov)
[ ] Do we want to show robots.txt on Production? (its default content is only to block everything for non-Prod) If so, we could link robots.txt to include /sitemap.xml
[ ] Any complications in using /sitemap.xml to link to other specialized sitemaps? (/sitemap.xml could link to /sitemap-search.xml, /sitemap-legal.xml, /sitemap-transition.xml, etc)
Future work
Other future work that may be needed following this issue's completion.
Summary
What we're after: We want to use sitemap.xml for both search engines and the specializations for search.gov. This ticket is to have a POC on a non-Prod space, and to do its initial QA
Related issues: Research into ways to create the sitemap: #5499 Document searech.gov sitemap requirements https://github.com/fecgov/fec-cms/issues/5501#issuecomment-1403877016 Policy and Guidance sitemap changes: https://github.com/fecgov/fec-cms/issues/5595
Completion criteria
Tech steps or considerations
Future work
Other future work that may be needed following this issue's completion.