When it comes to SEO knowledge about what can and can not be done with Google, a basic rule of thumb is : beware of what you read and how old it is. Once upon a time, it was regarded as common knowledge that Google can’t read querystrings on Urls – OK, I’m going back a way with that – but of course we all know that isn’t true nowadays.
I’ve done a few posts on setting up your DotNetNuke site with the new DotNetNuke social features, which includes configuring your DotNetNuke site to be a social network, and how to set up Vanity Urls for your DotNetNuke site using Url Master.
That’s all good, but there is a shortcoming in the DotNetNuke user profile design in that it doesn’t change the page title to reflect the current user that is being displayed. The page title stays at ‘User Profile for ifinity.com.au’, no matter which user is currently displayed.
Above : SERP Title is derived from the DNN Page Title, which is not user-specific for profile pages. This is taken from about a month ago.
(Do you want your Author profile to show up for your pages like in the screenshot? See my post on getting your Author Profile to show in Google Search Engine results)
What we really want is for the Page Title to show something specific to the content on the page. Assuming we want good SERP results for specific User pages, which is definitely the case if you have a Linked-In style directory. Or even to avoid having Google Webmaster Tools not complain that we have x,0000 duplicate Page Titles for our pages.
The code is this:
This would then set the page title to the person of which you’re currently viewing, by simply pulling the text for the ‘Register’ link.
This worked great as far as viewing the pages went :
I left that go for a while, to see what happened in Google.
Above : New Google SERP For the same link, taken at time of this blog post.
Wait, no so fast…
The Title is wrong. It should be ‘iFinity User Profile – Bruce Chapman’
(NOTE: You can see here my new search engine sitemaps have outranked my old search engine sitemaps – interesting..)
This is just the Google Author changes making their way across the web. In fact Google seems to have gone mad and Author-tagged any page it finds ‘Bruce Chapman’ on. And to think I felt it was an achievement to get just one Author tagged-SERP!
Those awake in the back row would have put their hand up and pointed out the obvious problem – the ‘dnn_dnnUser_RegisterLink’ only shows the logged-in user, not the user in the profile page. Google always crawls the web as an anonymous user, so won’t see the Display Name of the user when visiting the user profile.
A quick google of some other User profiles shows that this is true:
Apologies to Chris Hammond for using him as a guinea pig.
While this still brings up the Bruce_Chapman Url, what we can see is that the Page Title for this user profile has changed (ignore the fact it’s showing my Author profile again) – it says ‘iFinity User Profile – undefined’
With that result, I’ve been spurred on to test this out further.
But inspecting the SERP here, I can see that it has matched ‘Chris Hammond’ from the Journal feed on the user profile page. Which means that Google must be executing the Knockout code to load the dynamic content for the profile page.
The New Experiment
So now I’ve updated the code on the page to this:
(Hint : if you’re adding some script like this using a plain Text/Html module, then I suggest switching out of ‘rich text editor’ view and into ‘basic text box’ with ‘text’ view – otherwise your script will be stripped out when you update)
You’ll note that the script is much the same, except now it’s surrounded by a ‘setTimeout’ call, which waits for 1 second, then updates the page title. This should give enough time for the knockout to update the page title, but will it be enough for Google to read the new title and index it?
You can see the new Page TItle just by going to http://www.ifinity.com.au/Bruce_Chapman (or click on your own profile, if you have an account on this site)
Time will tell. You can google it yourself now to find out if it has been updated.
This technique is not limited to user profiles. If you have any type of 3rd party content that doesn’t update the page title to the way you like it, you should be able to experiment with changing the page title. This technique could be tried with blogs, e-comerce modules, forum posts – anything that isn’t updating the page title to your liking. It should be possible to also apply this technique to updating the page description as well, something else I will try as time goes by.
The reason I have posted this before the experiment is complete is to hopefully encourage others to try similar experiments with their own sites to see if this works OK, and can be used to expand the ability of DNN sites to be SEO optimised even when you’re up against a code-wall, where the underlying code doesn’t do exactly what you want. There’s always a way, after all.