core(config): show SEO audits in the UI#4057
core(config): show SEO audits in the UI#4057patrickhulce merged 6 commits intoGoogleChrome:masterfrom
Conversation
|
👍 |
| helpText: 'Pages with unsuccessful HTTP status codes may not be indexed properly. ' + | ||
| '[Learn more]' + | ||
| '(https://developers.goole.com/web/tools/lighthouse/audits/successful-http-code).', | ||
| '(https://developers.google.com/web/tools/lighthouse/audits/successful-http-code).', |
There was a problem hiding this comment.
| }, | ||
| 'seo-crawl': { | ||
| title: 'Crawling and Indexing', | ||
| description: 'To appear in search results, crawlers need access to your app.', |
|
a11y category has its own render logic at the moment, we'll need to refactor to make it part of default logic to render groups if they're present :) lighthouse/lighthouse-core/report/v2/renderer/category-renderer.js Lines 440 to 461 in 9ef858a |
26a7a26 to
6fde75d
Compare
| 'use strict'; | ||
|
|
||
| const parseURL = require('url').parse; | ||
| const URL = require('../../lib/url-shim'); |
There was a problem hiding this comment.
I missed that require('url').parse won't work in the extension. Thankfully it was easy to replace.
|
@patrickhulce thanks! I guess we don't want to create another custom renderer ATM? It doesn't make sense to make this refactor here IMO, it deserves its own PR. @rviscomi are we OK with launching w/o the categories? |
|
Yes, categories would be great to have but shouldn't block this PR. |
patrickhulce
left a comment
There was a problem hiding this comment.
that plan sgtm!
@kdzwinel any more changes you'd like to make? if not, this lgtm for initial release!
|
Sorry that I kept adding stuff after opening the PR. I should have put [WIP] in the title. Anyway, I have nothing more to add here. Thank you for reviewing it! |
no worries we all find things after the PR goes up :) this should go out with 2.7 today then! |
|
🎉 Fantastic! Thanks a bunch. |


Latest copy taken from the "Lighthouse SEO Audit Text" doc.
Tested in the extension:
I made sure that all "learn more" links work and link to the right docs (that's how I found that one of the links was broken ).
Closes #3772