{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 你好瞎i 的问题《How to provide canonical URL with Django HttpRespo》','https://www.manongdao.com/q-1354385.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
This question is very similar to one I just asked href: Can I get Google search results to use/display the final redirect url?, but now the question is specific to Django.
My site has webpage urls that use the following format:
www.mysite.com/id/pretty_title
The front page links to these pages, but the href actually contains some parameters:
www.mysite.com/id/?some_ugly_parameters_to_let_me_know_what_search_it_is_from
This then redirects to
www.mysite.com/id/pretty_title
which shows the page.
My issue is that Google's search results show the link to the page as the ugly url instead of the pretty redirected one.
What I have learned is that I need to provide a canonical link. But how can I do this when the ugly url page never really exists, at least not as one that I have written?
What happens server side is that the view of the ugly url does a redirect:
return HttpResponseRedirect(pretty_url)
You can just put it as part of the HTML returned from the Django template, in the
<head>section. Do you have abase.htmlin your Django? You can setup a{% block %}as a placeholder for the canonical URL and then set that value in each individual page that{% extends base.html %}base.html
I think this is the correct built template tag that you're looking for. {{ request.build_absolute_uri }}
A lot of these proposed solutions have issues if (1) you want your
wwwsubdomain to be the canonical one and (2) there are URL params in the request path.I would actually propose to hard code it in the base template and append
request.path.If you do end up wanting to use
build_absolute_uri, I would do it as follows in your view (or you could create a template function):Calling
build_absolute_uri()without an argument will callrequest.get_full_path()and append that to your domain. If a user finds your site viahttps://www.example.com/?param=123, your canonical URL will include that param.