After this lesson you can audit a site's security and mobile basics in ten minutes. Neither is glamorous, and neither is optional: both affect real visitors long before any ranking question.
HTTPS
HTTPS is HTTP over an encrypted connection. It prevents others on the network from reading or altering the page in transit and shows visitors that they are connected to the site they think they are. Browsers warn about plain HTTP pages, especially where forms are involved.
For search, here are the facts as documented. Google has described HTTPS as a lightweight ranking signal, and its canonicalisation guidance says it prefers HTTPS pages over HTTP when choosing among duplicates. Do not expect a jump in position from switching; do expect fewer warnings, less friction and cleaner signals. Also, certificate errors can affect redirects, which Google's guidance specifically warns about.
Moving to HTTPS
- Get a certificate for your domain. Many hosts offer this automatically at no extra charge; check your provider.
- Serve every page over HTTPS.
- Permanently redirect each HTTP URL to its HTTPS equivalent (redirects).
- Update canonical tags, internal links and sitemaps to HTTPS (canonicals).
- Fix mixed content: images, scripts or styles still requested over HTTP.
- Add the HTTPS version as a property in Search Console, and keep an eye on certificate expiry.
You can check a page for mixed content in the browser developer console, where warnings appear.
Mobile-friendly
Most web visits happen on phones in many markets, but do not rely on a guess about your audience: look at your own analytics (crawlers and analytics). What matters is that the page works on a small screen.
Mobile-first indexing
Google's documentation says that it predominantly uses the mobile version of a page for indexing and ranking. In practice:
- Content on the desktop version must also appear on mobile: text, images with alt text, links, structured data.
- Do not hide important content that only exists on desktop.
- The same metadata (title, description, robots tags) should be present on both.
- Googlebot for smartphones must be allowed to crawl your mobile pages and resources.
The simplest way to satisfy all of it is a responsive design: one URL and one HTML document that adapts to screen size with CSS. Google recommends responsive design as the easiest pattern to maintain.
The viewport tag
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Sourdough Classes | Crumb & Co.</title>
<style>
body { font-family: system-ui, sans-serif; line-height: 1.5; margin: 0; padding: 1rem; }
a.button { display: inline-block; padding: .75rem 1.25rem; background: #333; color: #fff; text-decoration: none; border-radius: 6px; }
</style>
</head>
<body>
<h1>Sourdough classes</h1>
<p>Text at a readable size, with a button large enough to tap.</p>
<a class="button" href="/classes/">See class dates</a>
</body>
</html>Without the meta viewport line a phone shows a shrunken desktop layout. This site's audit script errors when a built page lacks a viewport tag, because it is a cheap check with a big impact.
What good mobile pages have
- Text readable without zooming.
- Tap targets large enough and spaced apart.
- No horizontal scrolling.
- No intrusive pop-ups that cover content; Google has documented that intrusive interstitials can hurt the experience.
- Images and media that scale.
- Fast loading; see Core Web Vitals.
Preview your page at phone width with the HTML viewer by narrowing the window, and test on a real phone for touch behaviour.
Checking
- Open the site on your phone and complete the main task: find opening hours, book, buy.
- In Chrome's developer tools use the device toolbar to emulate screen sizes.
- In Search Console, URL Inspection shows how Googlebot sees the mobile page (Search Console basics).
- Use Lighthouse or PageSpeed Insights for a lab report; treat its score as a guide.
Common mistakes
- A site that mostly works over HTTPS with leftover HTTP resources.
- Redirecting HTTPS to HTTP, or leaving both versions live.
- A mobile site with less content or missing structured data compared with desktop.
- No viewport tag.
- Tiny tap targets, full-screen pop-ups and fixed headers that take half the screen.
- Letting the certificate expire.
- Blocking resource files needed for rendering the mobile page.
Exercise
On a site you know, test these five things and record yes or no: loads over HTTPS without a warning; HTTP redirects to HTTPS; no mixed content warnings in the console; has a viewport tag; the main call to action can be tapped easily on a phone. For each "no", write the fix.
Show how to read the result
A site that fails the redirect test lets two versions exist, so add a permanent redirect. A mixed-content warning means a hard-coded http:// image or script: change it to HTTPS. A missing viewport tag is a one-line fix in the head. Fix security items first, since visitors see warnings immediately.
Key points
- HTTPS encrypts traffic and builds trust; Google has said it uses HTTPS as a lightweight ranking signal and prefers it as the canonical.
- Move everything to HTTPS, redirect HTTP permanently, and fix mixed content.
- Google uses the mobile version of a page for indexing and ranking, so mobile content must match desktop.
- A responsive page with a viewport tag and readable, tappable content is the simplest approach.