Google search results lead to "Page not found" with wrong Statuscode 200

[tbreuss]

When googling for AlphaTab features, several search results lead to a "Page Not Found" page, but with a 200 Statuscode.

Googling for "alphatab barline":

The first two search results are leading to broken pages, that have a 200 status code.

On the one hand, this is annoying, but it is also not ideal for search engines, and therefore, of course, for the project itself.

I see two simple suggestions for improvement:

• Redirects with status code 301 could be configured on the website.
• Error pages should return the correct status code 404 or 410 for pages not found, or 5xx for error pages.

[Danielku15]

Unfortunately we do not own Google and I cannot make changes there 😆 Google will eventually need to scan our website and update their index accordingly.

As of now I have no plan to always maintain a potential list of redirects for old pages. Most of these pages are auto-generated and I tried to reduce the overhead on the number of generated pages.

Regarding the status code: that's how Docusaurus works. the website is a react single page application and there is no "server side" logic which could detect that Docusaurus will render a 404 page.