This project is read-only.

Multiple URLs send to same content - SEO Issues in BE 2.8

Jun 1, 2013 at 8:12 PM
I detected an issue in BE 2.8 related to duplicate content and SEO issues.

When you enable or disable the add date to the URL of the posts, BE does't redirect to the new URL creating duplicate content when reindexed by search engines.
For example, this link from
Lead us to the same content from this add date to url
Resulting in duplicate content as for the search engines. Also it happends when you change the root of the install folder of BE, for example:
For SEO purposes the 4 diferents URLs are duplicate content if not redirected to the correct URL
A 301 redirect could fix this issue, but the fix also have to check for extensionless URLs and WWW subdomains. I hope a patch could be released soon to fix this SEO issue.

P.D. I checked how wordpress deal with this issue, and seems to redirect to the correct URL in several ways. For example, all this URLs do a permanent redirect to the correct URL:
all do a 301 redirect to:
Jun 4, 2013 at 2:13 AM
I think that maybe this bug can be fixed by modifiyng the file post.aspx.cs and checking if the entry URL is different than the URL created by BE. If it is different then make a permanet redirect to the URL to avoid having 2 or more URLs to the same resource for a better SEO. Hope it help for make BlogEngine a better blogging platform. Thanks!
Jun 4, 2013 at 4:35 PM
Edited Jun 4, 2013 at 4:42 PM
I did the following change regarding the duplicate content issue with the default.aspx:

Both appear to Google as different pages with the same content. After I used the following quick fix the warning in Webmaster Tools has gone. Even the duplicate indexed default.aspx was removed from the Google Index.

default.aspx.cs, Method: protected void Page_Load(object sender, EventArgs e)
if (Request.RawUrl.ToLowerInvariant().Contains("default.aspx"))
        HtmlLink link = new HtmlLink();
        link.Href = "";
        link.Attributes["rel"] = "canonical";
I use BE 2.7 but it seems that BE2.8 works the same. Hope this helps...

Note: I should mention that I don't use post paging on my homepage, so maybe more work is required.
Mar 20 at 1:02 AM
Edited Mar 20 at 1:02 AM
I can understand this discusion in regard of anonymous browsing, whether by a User or by Search Engine, but have a question over the use of Ajax Postbacks when submitting a Comment.

I have an edge case I'm trying to solve!!

In the case of a Comment being posted, when post.aspx.cs get a new OnLoad event, with IsPostBack and IsCallback both true and the appropriate ID found, does the redirect still need to be done? I'm thinking that this is a User and the Response surely could be just to the URL being used.

Mar 20 at 2:25 PM
I have now the same problem with date in post., removing i have duplicate!
How can make to remove date in URL and make REDIRECT 301??

Can you help me?
Mar 30 at 7:14 AM
Edited Mar 30 at 8:57 AM
Hi Fabrizio and Others,

Latest version of BE does not have this issue any more.

Proof is here:

Have a great day!

Brian Keith Davis
Mar 30 at 9:42 AM
Thanks Brian,
i found solution for users of previous versions

It's here