Forum Moderators: martinibuster
[edited by: Sally_Stitts at 3:28 am (utc) on Jun 15, 2017]
Responsive? No. The identical page is served for both mobile and desktop.IMO there's no "ease" doing that, all that extra work. Much easier to just use bootstrap, a screen sniffer script and control presentation with CSS. Then there's no compromise with either.
The only difference is produced by my viewport setting, which I change according to each page's width (450-600 pixels). I have sacrificed big screen wonderfulness for ease of mobile implementation.
... easier to just use bootstrap, a screen sniffer script and control presentation with CSS
I did very well indeed in 2013That may have been the tipping point where mobile started to significantly steal traffic from Desktop. If I remember correctly, it was about the time I noticed a decline of revenue since I was not mobile responsive then. Still, it took me another year to go responsive.
Taking a shot at https this week. Not relishing that. Read some horror stories about the transition. Don't know what I am doing there, either.Upgrading to HTTPS should be straightforward if you follow the steps outlined here:
- Generic Steps to Switch from HTTP to HTTPS -
• Read all info at your host concerning certificates & switching to HTTPS and when applicable, follow those instructions.
• Install security certificate.
• Have you host enable HTTPS (if needed.) This will enable access from both HTTP & HTTPS.
• Go through site, page by page & make sure all file paths are relative (no protocol.) Test by accessing site using HTTPS and look for any browser alerts.
• Install 301 code in .htaccess fileNote: your server may require a different codeRewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
• Go through site again, page by page, and test. Any remote absolute links will need to be HTTPS including those found in scripts & pluggins. If you publish Adsence or other advertising, links in these scripts need to be HTTPS also (or just remove the protocol altogether.)
• Update sitemap.xml (if applicable) and submit to appropriate agencies (Google, Bing, Yandex, etc)
• In Google Search Council create a new site using HTTPS (do not use the Change of Address form.) It will take a few days to start populating information. This is normal & traffic to old site (HTTP) will drop off accordingly.
• Bing Webmaster Tools, Yandex & others should update automatically once they crawl your new pages. Updating/re-submitting sitemap.xml should speed up this process.