‘404 error-url’ not redirecting to new custom ‘404 url-page’

  • Resolved Cloud Development

    (@clouddevelopment)


    1 year, 9 months ago

    Hello,

    Thank you for making this plugin.
    It looks useful to enforce a custom 404-error-page, that is editable from inside WordPress. This plugin seems to do this neatly.

    Think I got a feature-request here:
    Redirect the ‘404 triggered-URL’, to the newly-selected ‘custom 404-page-URL’.
    So all ‘404 hits’ end-up in the browser with the same'(new)page-URL’.

    Currently; different 404-hits don’t give a URL redirect. The 404-page-content show the content of the custom page fine(thank you, as this plugin says it does).

    Or did I overlooked a setting……

    Looking forward to your replay,
    With kind regards,

Viewing 1 replies (of 1 total)
  • Plugin Author Peter Raschendorfer

    (@petersplugins)

    1 year, 6 months ago

    That’s exactly the difference between a redirect (HTTP status code 302, 303 or 307) and an “page not found” error (HTTP status code 404).

    Redireting to another URL tells Search Engines “this content exists, but has moved to another URL”. That has a completely different meaning.

    You should correctly inform Google & Co that the page does not exist and should be deleted from the index if necessary.

    Redirects should only ever be used between pages that are semantically equivalent or very similar. If used in any other way, Google will recognize the discrepancies. This can even have a negative impact on the ranking

    Regards,
    Peter

Viewing 1 replies (of 1 total)
  • The topic ‘‘404 error-url’ not redirecting to new custom ‘404 url-page’’ is closed to new replies.