Welcome to the Q&A Forum

Maybe Google is desperately trying to find a page which is replying within in reasonable delays... Time to first byte is horrible: http://www.webpagetest.org/result/151104_SQ_WXJ/1/details/ Apart from the speed issue - the 301 as proposed by Justin is the best solution; Dirk

Hey David, TripAdvisor doesn't use JavaScript to decide if you get the mobile version or note.  The server detects your useragent and then sends you the proper version of the site (on the same URL as you noted). Remember, JavaScript executes on your client.  So the JavaScript would have to be sent to your browser and then execute before it could figure out what kind of device you were on and then render the rest of the page.  That's basically how responsive design works, except that most commonly a CSS @Media Queries is used to determine the width of your viewport, and then the page is optimized for that width. What TripAdvisor does, is what Google calles a Dynamic website.  Basically the server handshakes with the browser before the page is sent, the server learns the useragent, and then sends different source code to the browser that is specific to that type of device/browser. You can read about the google definitions, I'm referencing here: https://developers.google.com/webmasters/smartphone-sites/details You can read a bit more about the SEO implications of the three approaches in this thread: http://www.seomoz.org/q/how-does-a-responsive-site-kill-seo I prefer to use Dynamic websites when the user tasks are likely to be different on different devices.  (i.e. Trip Advisor has a "Near Me Now" on smartphones, but not on the desktop). I prefer Responsive Design, when my content and user tasks are going to be the same on all devices, and only the formatting/presentation is going to be the same.  (such as reading a blog) I prefer separate URLs when the Information Architecture is going to be dramatically different on different devices, and it's unlikely that a single user is going to share URLs across multiple devices.  (Such as displaying a mobile boarding pass on a mobile phone, that I'd never offer on a desktop device, or scanning barcodes in a store). In many cases, you can combine all three.  I.E.  detect different devices on server to send different images and menus (Dynamic).  Use @media queries to optimize my content for the exact width of my current viewport (Responsive), and have a separate m.URL for mobile only pages, like that mobile boarding pass.  The cool buzzword for combining responsive and dynamic is called Responsive Design with Server Side Components or RESS (I have no idea what happened to the W or C in that acronym). I hope that helps! -Jason "Retailgeek" Goldberg.

Thanks for the "Good Answer" flag, David! I reformatted & added a little extra info to make the process a little clearer. Paul

Hi Aaron, thanks for the quick response and pointing me to the FAQs.

I don't know if it's on the list, but did you know that there is a wishlist you can contribute to? Visit http://seomoz.zendesk.com/forums/293194-seomoz-PRO-feature-requests and you can add your own feature requests, and others can vote on that request.