not sure why you can’t do both to be honest. Make your website templates RWD and it doesn’t matter what language you put it in.
But if you HAVE to choose then it depends on what you are selling and who you want to read it. If your user base is entirely English speaking mobile users then having a desktop website in Cantonese is not going to be very useful.
From an SEO point of view google does rank mobile friendly websites higher on mobile searches and the majority of the Western world speaks english so if that was where i was aiming at i’d make a good RWD english site first.
Do you have a lot of visitors using mobile? If so, concentrate on making your sites mobile-friendly.
Do you have a lot of international visitors? If so, it might be better to concentrate on international sites.
Do you have a lot of both? Then do both.
Only you can really judge what is the best strategy for your own business, but I think for the foreseeable future having mobile-friendly sites will be a must.
I don’t really understand what you’re asking here. Google regards links between a domain and its sub-domains as internal links, as it does with folders. SitePoint has recently moved away from having sub-domains or different domains to having everything under the main sitepoint.com domain, and has apparently seen an improvement in SEO results.
Yes, it’s something I thought was an interesting idea, but when I looked into it, it was confusing and I wasn’t sure if it were just a fad, or a standard for the future. I will maybe look again with time and try but with a simple site.
I use a PHP Framework and foolishly included common headings,footers, etc and Google was remarkably quick in detecting errors but very slow in acknowledging rectified pages. Needless to say Page ranking dropped immediately and it takes an infuriating amount of time to recover:(
Google does have very good and comprehensive testing tools which are absolutely necessary because they have introduced new HTML features which fail W3.org validation checks!
The following shows a web page using the AmpProject specifications. Try validating the page and also run a Web Page Speed Test.
Trailing numeric parameter selects the number of thumbnails.
I have just ran the Pingdom Speedtest and it takes just over half a second from the Californian server to display the first 53 items. Thousands of images are not shown until the thumbnails appear in the viewport.