Protocol-Relative Resource Links

What This Means

Resource links use protocol-relative URLs (starting with // rather than https:// or http://). For example: src="//example.com/script.js" rather than src="https://example.com/script.js".

Why It Matters for SEO

Protocol-relative URLs were popularized as a way to serve resources over the same protocol as the page. However, since HTTPS is now universal, they are considered bad practice: they rely on the page's protocol being correct; on HTTP pages, they serve resources over HTTP (creating mixed content); and they are confusing to read and maintain. Explicit HTTPS URLs are always safer and clearer.

What the Platform Checks

The platform identifies resource src or href attributes starting with // without an explicit protocol. Fires when protocol-relative URLs are found on resource elements (scripts, stylesheets, images).

How to Fix It

Replace all protocol-relative URLs with explicit https:// URLs:

• Before: src="//cdn.example.com/script.js"
• After: src="https://cdn.example.com/script.js"
• Update templates, CMS settings, and plugin configurations that generate protocol-relative URLs.