[docs-infra] Fix blog SEO for pagination #37926
Conversation
alexfauquette
added
scope: docs-infra
Netlify deploy previewhttps://deploy-preview-37926--material-ui.netlify.app/ Bundle size report |
There was a problem hiding this comment.
To fully help the bots and the UX, each blog page should be server-side rendered. https://deploy-preview-37926--material-ui.netlify.app/blog/?page=5 server response is still the one of the first page. Unless we do it like Vercel and Hashicorp, they have a load more button for their blog, not a pagination, and reference all the blog posts in their sitemap, e.g. https://vercel.com/crawled-sitemap.xml.
| const hrefWithSpecificPage = (newPage: number) => { | ||
| const tags = getTags(); | ||
|
|
||
| return `/blog/?${[ |
There was a problem hiding this comment.
Clicking on the first page should ideally not point to https://deploy-preview-37926--material-ui.netlify.app/blog/?. It should point to https://deploy-preview-37926--material-ui.netlify.app/blog/. This is to have more unicity of the URLs, hence less crawling budget spent on pages.
github-actions
bot
added
the
PR: out-of-date
|
I'm wondering if have a site map would not be another solution allowing google to simply crawl pages and even saving some crawl budget since blog posts are rarely updated |
@alexfauquette A sitemap could solve the SEO problem. Maybe we could do it the same way as for RSS: #35777. Some blog benchmark: https://www.notion.so/mui-org/docs-infra-Blog-52fdceef9eb04402a4ae99c845b98486.
|
|
Thanks for pointing to the RSS I was also wondering if a website could have multiple sitemap, it seems that yes |
danilo-leal
removed
the
website
|
What's the status of this PR? |
|
The will need another PR. I'm closing this one |
Use links for the blog pagination instead of buttons
Fix #40941
Iterate on https://www.notion.so/mui-org/Improving-the-blog-infrastructure-bcae2b15493f4daba0758adf499f7793?pvs=4#6f911b564cde48eeace27f51efcb6526