HTTPS Checker: Verify SSL & URL Structure on Any Page

RankNibbler's HTTPS checker verifies any URL uses HTTPS and audits the URL structure for SEO-damaging patterns: length, casing, underscores, excessive depth, tracking parameters, and trailing slashes. Catch silent URL issues before Google does. Free, instant, no signup.

Check a page now →

Why HTTPS Matters in 2026

Google confirmed HTTPS as a ranking signal in 2014, and the gap between HTTP and HTTPS sites has only widened since. By 2026, running an HTTP-only site is a functional non-starter for SEO and user trust. Here is why:

SSL certificates are effectively free (Let's Encrypt, Cloudflare, CloudFront) and renewal automation is built into every modern hosting platform. There is no excuse for running HTTP in 2026.

URL Structure Best Practices

CheckRecommendationWhy It Matters
ProtocolHTTPS alwaysRanking signal + security + browser warnings
LengthUnder 100 charactersGoogle truncates long URLs in SERPs; shorter is more shareable
CasingAll lowercaseCase-sensitive servers treat /Page and /page as different URLs; duplicate-content risk
SeparatorsHyphens, not underscoresGoogle treats hyphens as word separators, underscores as joins
Depth3-4 path levels maximumDeeper URLs are crawled less frequently and rank slightly worse
KeywordsInclude target termModest ranking signal and improved SERP snippet highlighting
No spaces or special charactersOnly a-z, 0-9, and hyphensEncoded characters (%20, %26) are ugly and sometimes break links
No dates if content is evergreenAvoid /2024/03/my-post unless time-boundDated URLs look stale when content stays relevant
Consistent trailing slashesPick one and stick to it/page and /page/ must not both return 200 — pick one

Common URL Problems This Checker Catches

Mixed HTTP and HTTPS

A site that has HTTPS on the main domain but serves some assets over HTTP. Browsers flag this as mixed content. Fix: ensure every internal link, image, script, and style sheet uses HTTPS.

Uppercase URLs

Mac/Linux servers treat /About and /about as different URLs. Google indexes them as duplicates, splitting ranking signals. Fix: enforce lowercase through server rewrites or canonical tags.

Underscores Instead of Hyphens

Google has repeatedly confirmed it treats keyword_one as a single token but keyword-one as two separate words. For multi-word URLs, hyphens are materially better for SEO.

Excessive Depth

URLs like /category/subcategory/topic/subtopic/article/page are crawled less frequently and rank worse than URLs closer to the root. Flatten your structure where possible.

Tracking Parameters in Canonicals

UTM parameters, session IDs, and filter parameters should never appear in canonical URLs. Set self-referencing canonicals without parameters to prevent duplicate-content issues.

Trailing Slash Inconsistency

If both /page and /page/ return the same content with 200 status, you have duplicate content. Pick one convention and 301-redirect the other.

How to Fix URL Issues

  1. Audit all URLs. Run the Site Audit to get a full list of URL issues across your site.
  2. Migrate to HTTPS if you haven't. Free certificates make this trivial. Set up 301 redirects from HTTP to HTTPS.
  3. Standardise URL format. Decide on lowercase-only, hyphen-separated, with or without trailing slash — then enforce at the server level.
  4. Fix specific issues with 301 redirects. Preserve link equity when changing URLs.
  5. Update internal links. Update to the new URL format directly; do not rely on redirects forever.
  6. Submit the updated sitemap. Help Google discover the canonical URLs quickly.

Related Technical SEO Tools