-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Links are not crawlable with acceptable URL #11818
Comments
Thanks for filing @JPPhoto! I'm really surprised this case of a valid cc @AVGP in case this should still be considered failing for a reason I'm not aware of :) |
@patrickhulce I should add that the URI is valid, whether or not the onclick JS is invoked. I get that Lighthouse would report an error iff the onclick handler tried to deceive the user; perhaps this is rather hard to detect and it's easier to flag instances as errors? Having not looked at the code, I don't know what's going on under the hood. |
1- we'd have to click every link and make sure the accompanying network request actually matches the provided href value... 2- we'd have to make sure that search/crawlers even try to resolve links with an onclick... or just ignore onclick and use href ? cc @AVGP any thoughts here? ideally we could just check for href and ignore all else ... but only if crawlers actually work like that :) |
So as far as Google Search is concerned, look at the |
thanks @AVGP! We'll mark a valid href + onclick handler as passing then 👍 |
I can pick this up @patrickhulce. Upon looking at the codebase, this is where the anchor is getting marked as failed.
|
The purpose of this audit is to flag links that are not crawlable.
We aren't. This change is about considering an anchor valid if it has a valid |
fixed by #13105. shipped in LH 8.6.0 |
Provide the steps to reproduce
What is the current behavior?
I see "Links are not crawlable" for this element:
What is the expected behavior?
Since the full link is crawlable, I wouldn't expect to see this error. The link has urlencoded parts, so perhaps that's triggering an issue; opening the URL in a browser shows the expected page.
Environment Information
Related issues
The text was updated successfully, but these errors were encountered: