Timeline for Wrong URL Requested But I know what they meant - 404 vs canonical vs 301 redirect
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 1, 2017 at 14:20 | comment | added | user2044510 | Excellent. Thanks. I've implemented this and it's working great. I had some RewriteRules that were too loose and they created a ton of duplicate content issues. Now I'm going through the site and fixing everything up. | |
| Nov 1, 2017 at 14:18 | vote | accept | user2044510 | ||
| Nov 1, 2017 at 12:54 | comment | added | MrWhite | Yes, a 301 (permanent) redirect. It's a mistyped URL - which is never going to be the real URL - so a permanent redirect (that is cached by browsers and recognised by crawlers) is the way to go. | |
| Nov 1, 2017 at 12:51 | history | edited | MrWhite | CC BY-SA 3.0 |
Clarified 301 redirect, minor improvements.
|
| Nov 1, 2017 at 12:45 | comment | added | user2044510 | Thanks a ton for all of that. So when you say I should redirect the incorrect url to the correct one I'm assuming it should be a 301? It's definitely not a 302 and I don't want it to issue a 200 in the header for a url that doesn't exist. So just give em a straight up 301 and be done with it? | |
| Nov 1, 2017 at 12:28 | history | answered | MrWhite | CC BY-SA 3.0 |