Should i redirect “ugly” url to friendly url?
I use mod_rewrite to rewrite https://example.com/?page=some-page&tab=2
to https://example.com/articles/some-page/2
. But people can still access both URLs.
I want to know: should i redirect the "ugly" URL to the friendly URL?
Does that improve my SEO? And why?
seo htaccess mod-rewrite
add a comment |
I use mod_rewrite to rewrite https://example.com/?page=some-page&tab=2
to https://example.com/articles/some-page/2
. But people can still access both URLs.
I want to know: should i redirect the "ugly" URL to the friendly URL?
Does that improve my SEO? And why?
seo htaccess mod-rewrite
add a comment |
I use mod_rewrite to rewrite https://example.com/?page=some-page&tab=2
to https://example.com/articles/some-page/2
. But people can still access both URLs.
I want to know: should i redirect the "ugly" URL to the friendly URL?
Does that improve my SEO? And why?
seo htaccess mod-rewrite
I use mod_rewrite to rewrite https://example.com/?page=some-page&tab=2
to https://example.com/articles/some-page/2
. But people can still access both URLs.
I want to know: should i redirect the "ugly" URL to the friendly URL?
Does that improve my SEO? And why?
seo htaccess mod-rewrite
seo htaccess mod-rewrite
asked 1 hour ago
515948453225
303
303
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It creates duplicate content issue and Search Engines dislike duplicate content.
Ugly url MUST be validly redirect to seo friendly URLs to avoid duplicate content/pages issue.
add a comment |
You only need to redirect the "ugly" URL if you had changed the URL structure and the "ugly" URLs had already been indexed by search engines and/or linked to by third parties. In this case, it is essential to redirect the old "ugly" URLs in order to preserve SEO.
However, if you implemented the "pretty" URLs from the very beginning - and these are the only URLs being referenced, then it's unlikely that redirecting the "ugly" URLs would make any difference in terms of SEO. You should already have the appropriate rel="canonical"
tags in-place, which further negates the requirement to implement redirects from the "ugly" URLs.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "45"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f119870%2fshould-i-redirect-ugly-url-to-friendly-url%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It creates duplicate content issue and Search Engines dislike duplicate content.
Ugly url MUST be validly redirect to seo friendly URLs to avoid duplicate content/pages issue.
add a comment |
It creates duplicate content issue and Search Engines dislike duplicate content.
Ugly url MUST be validly redirect to seo friendly URLs to avoid duplicate content/pages issue.
add a comment |
It creates duplicate content issue and Search Engines dislike duplicate content.
Ugly url MUST be validly redirect to seo friendly URLs to avoid duplicate content/pages issue.
It creates duplicate content issue and Search Engines dislike duplicate content.
Ugly url MUST be validly redirect to seo friendly URLs to avoid duplicate content/pages issue.
answered 1 hour ago
Nandla
3563
3563
add a comment |
add a comment |
You only need to redirect the "ugly" URL if you had changed the URL structure and the "ugly" URLs had already been indexed by search engines and/or linked to by third parties. In this case, it is essential to redirect the old "ugly" URLs in order to preserve SEO.
However, if you implemented the "pretty" URLs from the very beginning - and these are the only URLs being referenced, then it's unlikely that redirecting the "ugly" URLs would make any difference in terms of SEO. You should already have the appropriate rel="canonical"
tags in-place, which further negates the requirement to implement redirects from the "ugly" URLs.
add a comment |
You only need to redirect the "ugly" URL if you had changed the URL structure and the "ugly" URLs had already been indexed by search engines and/or linked to by third parties. In this case, it is essential to redirect the old "ugly" URLs in order to preserve SEO.
However, if you implemented the "pretty" URLs from the very beginning - and these are the only URLs being referenced, then it's unlikely that redirecting the "ugly" URLs would make any difference in terms of SEO. You should already have the appropriate rel="canonical"
tags in-place, which further negates the requirement to implement redirects from the "ugly" URLs.
add a comment |
You only need to redirect the "ugly" URL if you had changed the URL structure and the "ugly" URLs had already been indexed by search engines and/or linked to by third parties. In this case, it is essential to redirect the old "ugly" URLs in order to preserve SEO.
However, if you implemented the "pretty" URLs from the very beginning - and these are the only URLs being referenced, then it's unlikely that redirecting the "ugly" URLs would make any difference in terms of SEO. You should already have the appropriate rel="canonical"
tags in-place, which further negates the requirement to implement redirects from the "ugly" URLs.
You only need to redirect the "ugly" URL if you had changed the URL structure and the "ugly" URLs had already been indexed by search engines and/or linked to by third parties. In this case, it is essential to redirect the old "ugly" URLs in order to preserve SEO.
However, if you implemented the "pretty" URLs from the very beginning - and these are the only URLs being referenced, then it's unlikely that redirecting the "ugly" URLs would make any difference in terms of SEO. You should already have the appropriate rel="canonical"
tags in-place, which further negates the requirement to implement redirects from the "ugly" URLs.
answered 41 mins ago
MrWhite
30.5k33364
30.5k33364
add a comment |
add a comment |
Thanks for contributing an answer to Webmasters Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwebmasters.stackexchange.com%2fquestions%2f119870%2fshould-i-redirect-ugly-url-to-friendly-url%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown