GoogleChrome/lighthouse

Add guidance about preferring secure canonical links

Open

#4700 opened on Mar 6, 2018

View on GitHub
 (5 comments) (0 reactions) (1 assignee)JavaScript (27,768 stars) (9,278 forks)batch import
P3good first issue

Description

Consolidate duplicate URLs says that Google Search prefers HTTPS. It looks like the audit already has the ability to flag specific issues. I'd be willing to take a stab at this and contribute my first true code to the repo, if y'all think this is worthwhile.

Contributor guide

Tech stack
javascriptnodejs
Domain
frontendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptNode.jsLighthouse audit structureSEO knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the current audit code for duplicate URLs. Locate the existing canonical link checks in the Lighthouse audit definitions. Add a recommendation to prefer HTTPS for canonical URLs. Reference Google's documentation on consolidating duplicate URLs. Consider extending an existing audit or creating a new one.