Mobile Site Annotations
-
Our company has a complex mobile situation, and I'm trying to figure out the best way to implement bidirectional annotations and a mobile sitemap. Our mobile presence consists of three different "types" of mobile pages:
-
Most of our mobile pages are mobile-specific "m." pages where the URL is completely controlled via dynamic parameter paths, rather than static mobile URLs (because of the mobile template we're using). For example: http://m.example.com/?original_path=/directory/subdirectory. We have created vanity 301 redirects for the majority of these pages, that look like http://m.example.com/product that simply redirect to the previous URL.
-
Six one-off mobile pages that do have a static mobile URL, but are separate from the m. site above. These URLs look like http://www.example.com/product.mobile.html
-
Two responsively designed pages with a single URL for both mobile and desktop.
My questions are as follows:
-
Mobile sitemap: Should I include all three types of mobile pages in my mobile sitemap? Should I include all the individual dynamic parameter m. URLs like http://m.example.com/?original_path=/directory/subdirectory in the sitemap, or is that against Google's recommendations?
-
Bidirectional Annotations: We are unable to add the rel="canonical" tag to the m. URLs mentioned in section #1 above because we cannot add dynamic tags to the header of the mobile template. We can, however, add them to the .mobile.html pages. For the rel="alternate" tags on the desktop versions, though, is it correct to use the dynamic parameter URLs like http://m.example.com/?original_path=/directory/subdirectory as the mobile version target for the rel="alternate" tag? My initial thought is no, since they're dynamic parameter URLs. Is there even any benefit to doing this if we can't add the bidirectional rel="canonical" on those same m. dynamic URLs?
I'd be immensely grateful for any advice! Thank you so much!
-
-
Yup, you've got it!
-
Thanks for the great advice, Kristina! I really appreciate it.
You raise a good point on the vanity vs. parameter URL risks. We primarily use these static 301 vanity URLs for ad campaigns and media buys, so we're not using them in any internal linking. The template we use for our mobile environment, called Kony, doesn't actually have "links" on the back end of the site the same way a desktop site would - they're more like buttons that load a specific set of content without using a unique, canonical URL for that content - this is why all of our mobile pages on this environment are parameter URLs based on the user path, not "real" URLs. Weird, I know!
I think that's an excellent idea to specify in Webmaster Tools that our mobile parameters determine our content, just so Google knows.
So just to confirm your recommendations around the mobile sitemap - we should create a single sitemap that includes the parameter URLs (http://m.example.com/?original_path=/directory/subdirectory) as well as the static .mobile.html pages (http://www.example.com/product.mobile.html)? There is no content overlap between the two environments. I assume we should not include the responsive design URLs, since they're not exclusively mobile URLs?
Thanks again!
-
Hi Critical Mass,
Before I answer your direct questions, I think you're putting yourself in a tricky situation by creating vanity 301 redirects to those dynamic mobile URLs. If someone ever links to the mobile version of your page, they're going to use the URL with parameters, because that's the page they end up on. That means that all inbound links will point Google to your parameter URLs and all internal links will point to the static URLs you've created. Link equity will be split, and all pages will suffer for it.
It's true that Google understands static URLs a bit better than it understands URLs built with parameters, but it does understand that sometimes parameters define content. I recommend getting rid of those static URLs, then using Google Webmaster Tools to explicitly say, "these parameters define content." You can learn more about how to do this here: https://support.google.com/webmasters/answer/1235687?hl=en
Now, to answer your questions:
-
You should only include the URLs that you want Google to index. If you follow my recommendation above, this is now an easy question to answer.
-
Yes, use the rel="alternate" tag on your desktop pages! Like I said, Google understands that parameters can determine content. You want to connect the two pages as much as possible, even if you can't canonical back.
Hope this helps!
Kristina
-
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Site with both subfolders and subdomains
Hi everyone,
Intermediate & Advanced SEO | | medi_
I'm working on a website that has a quite extensive subfolder structure for product and multilingual purposes.
domain.com/en
domain.com/it
domain.com/fr
domain.com/en/category
domain.com/it/category
domain.com/fr/category
domain.com/en/category/product
domain.com/it/category/product
domain.com/fr/category/product
domain.com/en/category/product/region
domain.com/it/category/product/region
domain.com/fr/category/product/region
and so on... We will soon be launching a completely different service, which would make the subfolder structure become even more complex. As John Mueller recently stated that Subdomains and Subfolders are treated the same by Google, I am now considering building that new service under subdomains for product reason, and for the sake of clarity. 1- Would my subdomains inherit the authority of my main domain?
2- Do I have to keep the language folders with the subdomain structure?
e.g.:
new-service.domain.com/en
nouveau-service.domain.com/fr
nuovo-servizio.domain.com/it OR
new-service.domain.com
nouveau-service.domain.com
nuovo-servizio.domain.com Looking forward to reading you!0 -
Existing 301s during site migration - what to do?
Hi - I'm looking at an old website and there are lots of 301s internal to that site - what do I do with these when I move to a new site? Should I list them and adjust them so they redirect to the new site now (instead of from one URL to another URL on the old site) - I'm thinking that if I don't the user will have to travel through one 301 then another to get to the new site, which doesn't seem like a great idea? Your thoughts would be welcome.
Intermediate & Advanced SEO | | McTaggart0 -
Is this ok for content on our site?
We run a printing company and as an example the grey box (at the bottom of the page) is what we have on each page http://www.discountbannerprinting.co.uk/banners/vinyl-pvc-banners.html We used to use this but tried to get most of the content on the page, but we now want to add a bit more in-depth information to each page. The question i have is - would a 1200 word document be ok in there and not look bad to Google.
Intermediate & Advanced SEO | | BobAnderson0 -
Site duplication issue....
Hi All, I have a client who has duplicated an entire section of their site onto another domain about 1 year ago. The new domain was ranking well but was hit heavily back in March by Panda. I have to say the set up isn't great and the solution I'm proposing isn't ideal, however, as an agency we have only been tasked with "performing SEO" on the new domain. Here is an illustration of the problem: http://i.imgur.com/Mfh8SLN.jpg My solution to the issue is to 301 redirect the duplicated area of the original site out (around 150 pages) to the new domain name, but I'm worried that this could be could cause a problem as I know you have to be careful with redirecting internal pages to external when it comes to SEO. The other issue I have is that the client would like to retain the menu structure on the main site, but I do not want to be putting an external link in the main navigation so my proposed solution is as follows: Implement 301 redirects for URLs from original domain to new domain Remove link out to this section from the main navigation of original site and add a boiler plate link in another area of the template for "Visit xxx for our xxx products" kind of link to the other site. Illustration of this can be found here: http://i.imgur.com/CY0ZfHS.jpg I'm sure the best solution would be to redirect in URLs from the new domain into the original site and keep all sections within the one domain and optimise the one site. My hands are somewhat tied on this one but I just wanted clarification or advice on the solution I've proposed, and that it wont dramatically affect the standing of the current sites.
Intermediate & Advanced SEO | | MiroAsh0 -
URL strategy mobile website
Hello everyone, We are facing a challenging decision about where our website (Flash Gaming website) is going. We are in the process of creating html5 games in the same theme of the flash games that we provide to our users. Now our main concern is to decide how to show this new content to the user? Shall we create brand new set of urls such as : http://www.mydomain.com/games/mobile/kids/ Or shall we adapt the main desktop url : http://www.mydomain.com/games/kids/ and show the users two different versions of the page depending on whether they are using a mobile device (so they see a mobile version) or a pc/laptop (so they a see desktop version). Or even redirect people to a sub-domain : http://m.mydomain.com/ The main idea we had is to keep the same url structure, as it seems that google is giving the same search results if you are using a mobile device or not. And creating a new set of urls or even a sub-domain, may involve a lot of work to get those new links to the same PA as the desktop URL that is here and know since a while now. Also the desktop page game should not be accessible to the mobile devices, so should this be redirected (301?) to the mobile homepage of the site? But how google will look at the fact that one url is giving 2 different contents, CSS etc, and also all those redirects might look strange... we are worried that doing so will hurt the page authority and its ranking ... but we are trying to find the best way to combine SEO and user experience. Any input on this will be really appreciated. Cheers,
Intermediate & Advanced SEO | | drimlike0 -
Our Site's Content on a Third Party Site--Best Practices?
One of our clients wants to use about 200 of our articles on their site, and they're hoping to get some SEO benefit from using this content. I know standard best practices is to canonicalize their pages to our pages, but then they wouldn't get any benefit--since a canonical tag will effectively de-index the content from their site. Our thoughts so far: add a paragraph of original content to our content link to our site as the original source (to help mitigate the risk of our site getting hit by any penalties) What are your thoughts on this? Do you think adding a paragraph of original content will matter much? Do you think our site will be free of penalty since we were the first place to publish the content and there will be a link back to our site? They are really pushing for not using a canonical--so this isn't an option. What would you do?
Intermediate & Advanced SEO | | nicole.healthline1 -
On-Site Optimization Tips for Job site?
I am working on a job site that only ranks well for the homepage with very low ranking internal pages. My job pages do not rank what so ever and are database driven and often times turn to 404 pages after the job has been filled. The job pages have to no content either. Anybody have any technical on-site recommendations for a job site I am working on especially regarding my internal pages? (Cross Country Allied.com)
Intermediate & Advanced SEO | | Melia0 -
Mobile subdomain recommendations - Mobile SEO
My company is moving forward with creating a subdomain for mobile visitors (m.examplesite.com). I know there is much discussion on subdomain vs one url with different style sheets. That ship has sailed and the subdomain is the way we are proceeding. Google appears to recommend leaving both sites open to the normal Googlebot and redirecting the mobile bot to the mobile site (as we will be redirecting mobile visitors to the mobile subdomain). Has anyone had experience with this. Any duplicate content issues? Does anyone feel strongly that the normal Googlebot should be blocked from the mobile site (this seems to go against Google's recommendations)? It seems like another option is to use the canonical tag and let the search engines know the traditional site is the canonical page/version. Any recommendations? Any other issues that should be considered?
Intermediate & Advanced SEO | | btdavis0