Update sitemap.xml to include live strategies about frontend

[kenkunz]

I have discovered some issues with our current sitemap.xml that I think are worth addressing.

1. sitemap.xml includes references to nested sitemaps

Our current sitemap.xml includes references to:

• https://tradingstrategy.ai/api/sitemap/exchanges/sitemap.xml
• https://tradingstrategy.ai/blog/rss.xml
• https://tradingstrategy.ai/docs/sitemap-docs.xml
• https://tradingstrategy.ai/api/sitemap/pairs/paged/0.xml (and 4 additional pages)

As a rule, sitemaps should include entries for pages, and sitemap indexes should include references to other sitemaps. A sitemap itself should not include nested sitemap entries.

See:

• Google: Manage your sitemaps with a sitemap index file
• Stack Overflow: Multiple sitemaps within single sitemap file

Recommended solution

Create a sitemap index served from /sitemap.xml which references other sitemaps.

Alternatively, we could read all other sitemaps and compose a single sitemap.xml. This seems more cumbersome and costly, and may result in size or performance issues down the road.

[kenkunz]

2. Nested sitemaps served from invalid path nodes

Our nested sitemaps for exchanges and pairs are at a different node in the page hierarchy than the pages they reference.

Per Google's documentation linked below:

Sitemaps that are referenced in the sitemap index file must be in the same directory as the sitemap index file, or lower in the site hierarchy. For example, if the sitemap index file is at https://example.com/public/sitemap_index.xml, it can only contain sitemaps that are in the same or deeper directory, like https://example.com/public/shared/....

See:

• Google: Sitemap index best practices

Recommended solution

This could be fixed by having a frontend proxy that serves these resources from the correct path node. E.g., /trading-view/sitemap-exchanges.xml route would proxy the content from /api/sitemap/exchanges/sitemap.xml. The proxy route is what would be included in the sitemap index.

[kenkunz]

3. Blog and Glossary sitemaps

Our current sitemap.xml does not include the glossary sitemap (even with the "incorrect" nesting approach).

Blog posts are currently via /blog/rss.xml, which is not a valid format within a sitemap index.

Recommended solution

Use a sitemap index (see 1. above) and include /glossary/sitemap.xml as well as a new /blog/sitemap.xml.