Issue Bug Closed

#94566404 page handling is not SEO optimized

Rozbeh Chiryai Sharahi 07/16/21, 10:17 updated 08/05/24, 19:14

Description

Hello,

i think this I celebrate my 15th year working with TYPO3. And still TYPO3 has no good 404 handling.

Current problem appearing on v9.

Let’s say we have a site configuration:

site-1 -> base: http://my.url/site-1
site-2 -> base: http://my.url/site-2

Going to http://my.url/site-1/some-not-existing-page leads to a 404 (correct)
Going to http://my.url/site-2/some-not-existing-page leads to a 404 (correct)
Going to ttp://my.url/some-not-existing-page leads to a redircet to site-1 (not-correct)

[ADD_DESCRIPTION_OF_MIDDLEWARE_STACK_PROBLEM_AND_ADD_SOLUTION_PROPOSEL]

I can already guess that some will argument that this is a SEO related issue that is not the responsibility of TYPO3 core. Well if you think so…

Kind regards
Rozbeh

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 6

  1. Rozbeh Chiryai Sharahi changed description 07/16/21, 10:18

  2. Benni Mack changed is private 10/13/21, 14:54

  3. Benni Mack commented and changed status New Needs Feedback 11/03/22, 11:36

    Hey Rozbeh Chiryai Sharahi,

    thank you for your report.

    Since http://my.url/ has no site configuration, where do you expect to configure a fallback error handler then or how to solve this issue? If you feel that after 15 years, TYPO3 still has no good 404 handling, I would really like to know what can be improved in your situation.

    All the best,
    Benni.

  4. Rozbeh Chiryai Sharahi commented 11/03/22, 18:36

    Hello Benni Mack,

    I don’t remember “situation” back then anymore, but looking at the description I’d say, that from SEO point of view a 30x redirect of every URL which can not be resolved to a site is not correct.

    In the given example this is all a redirect:

    http://my.url/a -> 30x
    http://my.url/b -> 30x
    http://my.url/c -> 30x
    http://my.url/d -> 30x
    http://my.url/f -> 30x

    Possible solution imho:

    - Introduce a SiteNotFoundErrorHandler
    - Dispatch a site-not-found-event, so it can be handled (and document it)

    …

    Possible last fallback: Take the 404 handling of the first existing site.

    This could be done on middleware if not already the case in current TYPO3 versions.

    Kind regards
    Rozbeh Chiryai Sharahi

  5. Rozbeh Chiryai Sharahi commented 08/05/24, 17:14

    @benni In my opinion, this is already solved on version 13.

    Following I did:

    • Create a `site-1` with root-page-path `/site-1`
    • Create a 404 handling for that site
    • Navigate to `/site-1/does-not-exists` -> 404 handling of site triggered correctly
    • Navigate to `/does-not-exist` -> generic 404 page of typo3 appeared.

    => Perfect and ticket can be closed to my taste.

  6. Georg Ringer commented and changed status Needs Feedback Closed 08/05/24, 19:14

    closing as requested