Project

General

Profile

Actions
Copy link

Bug #94566

open

404 page handling is not SEO optimized

Added by Rozbeh Chiryai Sharahi almost 3 years ago. Updated over 1 year ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
SEO
Target version:
-
Start date:
2021-07-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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

Actions
Copy link
 #1

Updated by Rozbeh Chiryai Sharahi almost 3 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Benni Mack over 2 years ago

  • Private changed from Yes to No
Actions
Copy link
 #3

Updated by Benni Mack over 1 year ago

  • Status changed from New to Needs Feedback

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.

Actions
Copy link
 #4

Updated by Rozbeh Chiryai Sharahi over 1 year ago

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

Actions
Copy link

Also available in: Atom PDF