-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Fork the Chrome extension to demo SEO audits #3656
Comments
Do you have a link to install? |
@rviscomi it's up! Extension is unlisted, only accessible with this link: https://chrome.google.com/webstore/detail/lighthouse-seo/ckjgeicnedpfbjkleiahadaopannahkj I included #3657 which is waiting for merge , added a badge over the icon so this extension is easy to distinguish from the original one and removed all throttling because our audits don't need it. Let me know if I should change anything. If everything looks fine, please close this issue - I'll keep adding new audits regularly. |
Small nit: can we say "These checks ensure search engine crawlers understand your website." This makes the language consistent with the other sections :) |
Also @rviscomi- I think we're planning on doing a release of Lighthouse next week and another one later this month. When do you think this new section of the report could land? |
@vinamratasingal sorry, it looks like I haven't updated copy to the latest version yet. This description will say:
|
Ah OK, small nit on the copy. Can we say: (new changes highlighted in Italics) These checks ensure that your page is optimized for search engine results. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. |
LGTM |
@vinamratasingal thanks! I updated the description in the doc where we keep all copy so it doesn't get lost. |
Amazing, thanks folks :) Looking awesome |
To get feedback on the SEO audits before release, we'd like to be able to give testers a link to install an extension that has all completed audits in the SEO category enabled in the UI.
The text was updated successfully, but these errors were encountered: