Trying to figure out the best way to handle sitemaps
Unanswered
Nile Crocodile posted this in #help-forum
Nile CrocodileOP
So I used to have every single page in my
However, as I am restructuring the website and expanding want the website covers I am starting to rethink how I set up/handle sitemaps, especially as I update the routing structure to the website. For example,
Is it better to just cram everything into the root
/sitemap.xml
for my website but at some point Google stopped completely reading from it. It has been like 2 years since Google has read it according to the Search Console. Due to this I started creating /authors/sitemap/0.xml
, /news/sitemap/0.xml
, /college-football/rankings/sitemap/0.xml
and a custom API route for Google News sitemaps since Next.js doesn't support it yet /news-sitemap.xml
. The most I have in a single sitemap is 565 which is under /news/sitemap/0.xml
.However, as I am restructuring the website and expanding want the website covers I am starting to rethink how I set up/handle sitemaps, especially as I update the routing structure to the website. For example,
/news
is changing to /college/news
, and /news/[division]
and /news/[division]/[conference]
is changing to /college/[sport]/news/[division]
and /college/[sport]/news/[division]/[conference]
.Is it better to just cram everything into the root
sitemap.xml
or should I try creating sitemaps under the dynamic routes? However, sitemap.ts
does not have access to params so they would have to be custom API routes. Any ideas/help would be great!