Lighthouse SEO Score: 2026 Audit Guide

One forgotten tag can drag a perfect Lighthouse SEO score down to 69 overnight, and it is a classic launch-day mistake. A team copies a staging build to production, the robots meta tag still says noindex, and the green circle in Chrome turns orange. The fix takes minutes, but missing it is expensive, because the same tag that costs those points also tells Google to keep the page out of search.

The score is a fast smoke test for crawl and markup basics, not a ranking report. This guide explains what each of the ten scored audits checks, why one of them outweighs the rest, how to fix every failure, and what changed in Lighthouse 12 and 13. Our take up front: get every audit that applies to your page to pass, then spend your time on the things Lighthouse cannot see.

What is the Lighthouse SEO score?

The Lighthouse SEO score is a number from 0 to 100 that Chrome's Lighthouse tool gives a page after ten automated checks on crawlability and markup. It tells you whether search engines can read and index the page, but it does not measure content quality, links, or real user speed, and nothing in Google's guidance says it ranks pages by it.

Lighthouse is the open source auditing tool built into Chrome DevTools, and it also powers the lab section of PageSpeed Insights, which runs it for the Performance, Accessibility, Best Practices, and SEO categories.

Lighthouse itself says there are "many additional factors Lighthouse does not score here that may affect your search ranking," which is the most honest line in the report. Our technical SEO audit process shows where a Lighthouse run fits among the checks that follow it.

Which audits does the Lighthouse SEO category run in 2026?

The SEO category scores ten audits in 2026: indexing permission, HTTP status code, crawlable links, robots.txt validity, document title, meta description, descriptive link text, image alt text, hreflang, and canonical. A separate structured data item is a manual check with no weight, and every scored audit is a simple pass or fail for the page.

The list comes from the Lighthouse default configuration, and the middle column paraphrases each audit's own description. The weight column is copied from the configuration.

Audit	What it checks	Weight
Page is blocked from indexing	Noindex in meta tag, header, or robots.txt	About four
Document has a title element	A title element exists	One
Document has a meta description	A description tag exists and is not empty	One
Successful HTTP status code	The page does not return an error code	One
Links have descriptive text	No generic anchors like click here	One
Links are crawlable	Every link has a usable href	One
robots.txt is valid	The file parses and the server answers	One
Image alt attributes	Images carry alt text	One
Valid hreflang	Language codes and URLs are well formed	One
Valid canonical	The canonical link is sane	One

The title and alt text checks come from the accessibility side of Lighthouse, because screen readers need them as much as crawlers do, and our web accessibility and SEO guide covers that overlap.

Why does one failing audit cost so much more than the others?

The indexing audit carries a weight of 93 divided by 23, which is about four, while every other SEO audit weighs one. Lighthouse set it that way so that a blocked page fails the whole category on its own, and if that single audit fails while everything else passes, the score drops to about 69.

A comment in the configuration says the indexing audit should carry at least 31 percent of the score, so that its failure alone fails the category. The ten weights add up to about 13, and the indexing audit holds about four of them. Our own arithmetic from those weights says one ordinary failure takes a page from 100 to about 92, and two bring it to about 85, assuming all ten audits apply. That matches how search works, because a missing description costs a better snippet while a blocked page does not appear at all.

Does a perfect Lighthouse SEO score help you rank?

No. Google's guidance names Core Web Vitals, not this score, as used for ranking, and its page experience guidance says good results in third-party tools do not guarantee top rankings. The same guidance warns that chasing a perfect score just for SEO may not be the best use of your time.

Google's page experience documentation says Core Web Vitals are used by its ranking systems, then adds that good results in reports "or third-party tools" do not guarantee that pages "will rank at the top of Google Search results." Core Web Vitals come from real users in the field, while the SEO category comes from one simulated load in a lab, so the two answer different questions. Our Core Web Vitals guide explains the field side.

Our take: a page that scores 100 can still sit on page five, while a page that scores 92 can sit in first place. The audits protect you from silent failures, such as a leftover block or a canonical tag that points at the homepage, and those matter far more than the number.

How do you fix "Page is blocked from indexing"?

Find which of three places is blocking the page and remove the block: a robots meta tag set to noindex or none, an X-Robots-Tag HTTP header with the same values, or a robots.txt rule that disallows the URL. Lighthouse checks all three, so fix the source and rerun the audit.

The Lighthouse source flags the values noindex and none, along with an unavailable_after date that has already passed, and it reads them from both the robots meta tag and the X-Robots-Tag response header. A common cause is a launch, because a staging site carries a block on purpose and the setting rides along into production, which our staging site SEO guide shows how to prevent. Header blocks never appear in the page source, so check the DevTools Network panel too.

Before you remove a block, confirm that it is a mistake, because thank-you pages, internal search results, and login screens often belong outside the index. Our robots.txt and noindex guide explains when each tool fits, including why a robots.txt rule stops crawling but not indexing.

How do you fix title, meta description, and image alt failures?

Add the missing element. The title audit fails when a page has no title element, the meta description audit fails when the tag is missing or empty, and the alt audit fails when an image has no alt attribute. Lighthouse checks presence rather than quality, so a pass is only the first step.

Lighthouse does not judge whether a title is compelling or a description fits the page, so a title that reads "Home" passes, and so does a description copied onto five hundred pages. Google often rewrites titles it finds vague or stuffed, as our guide to Google title link rewrites shows, and descriptions shape clicks rather than rankings, which our meta description guide covers.

Alt text describes an image for people using screen readers and gives search engines context for image search. Decorative images can carry an empty alt attribute, which still passes because the attribute exists, and our image alt text guide explains how to write alt text that helps both groups.

Why does Lighthouse flag your links and your link text?

Two audits look at links. The crawlable links audit fails when an anchor has no usable destination, such as an empty href, a javascript void link, or a click handler with no href, and the link text audit fails when anchors use generic phrases like click here, read more, or learn more.

Search engines follow href values, so a link built only on a click handler is a dead end for a crawler. The English list of generic phrases also includes here, more, see more, and this.

Our take: that list is short, and an anchor like "our guide" passes while still saying little, so write anchors that name the destination. Our internal linking strategy guide shows how descriptive anchors also build topic clusters.

What do the canonical and hreflang audits catch?

The canonical audit fails when a page declares conflicting canonical URLs, an invalid or relative URL, a URL that points to an hreflang alternate, or the site's homepage from a deeper page. The hreflang audit fails when a language code is not recognized or an alternate URL is relative, and neither audit can tell you whether Google accepts your choice.

The homepage case tends to come from templates that hard-code the root URL as the canonical for every page. Pages with no canonical tag are marked not applicable, so a missing tag costs nothing, but on sites with filters or tracking parameters it is still a risk, which our canonical tags guide covers.

Take a retailer in Munich with German pages for Germany and Austria and an English version for the US. A typo in the language code or a relative alternate URL fails the audit, but a wrong region code or a missing return link does not, because the audit validates only the language part of each code and checks one page at a time. Our hreflang and international SEO guide covers the full setup.

When do the status code and robots.txt audits fail?

The status code audit fails when the page returns any code from 400 to 599. The robots.txt audit fails when the file is malformed or when the server answers with a 5xx error or a 429 rate limit, while a missing robots.txt that returns a 404 is marked not applicable and costs nothing.

Soft errors slip through. A page that shows "not found" text with a success status passes this audit, even though Google may treat it as a soft 404, and our HTTP status codes guide explains the difference. When robots.txt loads, Lighthouse validates each line and lists any it cannot parse.

Our take: treat a robots.txt server error as urgent, because the same error that fails this audit also reaches search engine crawlers when they request the file.

What changed in the Lighthouse SEO category since 2024?

Lighthouse 12, released April 22, 2024, reorganized the SEO category. The indexing audit got enough weight to fail the category alone, the viewport and font size audits moved to Best Practices, the plugins audit was removed, and tap targets were replaced by an accessibility audit. Lighthouse 13 later removed the font size audit entirely.

The Lighthouse changelog says the update was made "to reflect the priorities of Google search in 2024," which is why a tutorial that tells you to fix tap targets for SEO was written for an older version. Lighthouse 13.0.0 shipped on October 10, 2025 with "remove font-size audit" in its notes, and the latest release at the time of writing is 13.5.0, dated September 17, 2026. Mobile checks still matter for search, as our mobile-first indexing guide explains, but Lighthouse no longer scores them as SEO items.

What is the new agentic browsing category in Lighthouse?

Agentic browsing is a separate Lighthouse category added in version 13 during 2026. It checks how well a page works for AI agents, with audits for the accessibility tree, WebMCP forms and tools, layout shift, llms.txt, and agent resource discovery. It is not part of the Lighthouse SEO score and does not change it.

Version 13.2.0 added the category, and version 13.3.0, dated May 7, 2026, put it in the default configuration. Our take: watch it, but do not build for it yet, because an llms.txt file is a bet on how AI tools may read a site rather than a Google Search requirement. Our llms.txt explainer covers what the file does and does not do.

How should you run Lighthouse for SEO checks?

Run Lighthouse from Chrome DevTools or PageSpeed Insights on one URL per template rather than just the homepage, and select only the SEO category to keep runs fast. Read the failing audits instead of the score, rerun after each fix, and pair Lighthouse with a crawler and Search Console for whole-site coverage.

For an online store in Austin, Texas, the templates are the homepage, a category page, a product page, and a blog post. A short routine covers them:

• Pick one live URL for each template, not one URL for the whole site.
• Run the SEO category on the live URL, not on a local or staging copy.
• Expand every failing audit and note the exact element or header it names.
• Fix the template, not the single page, so the change reaches every URL that shares it.
• Rerun the audit on the same URL and save the report next to the change log.
• Repeat after every release that touches templates, headers, or robots.txt.

PageSpeed Insights runs the same audits for you and shows field data from real Chrome users next to the lab results. Teams in Seoul, South Korea face one extra step, because much of Korean search runs on Naver, which has its own webmaster tool, and our Naver SEO guide covers what to check there.

What does the Lighthouse SEO score not check?

The Lighthouse SEO score ignores content quality, search intent, backlinks, internal link depth, duplicate content across pages, structured data validity, real user speed, and whether Google has indexed the page. Those factors decide rankings, so cover them with Search Console, a crawler, and manual review.

Structured data is the clearest gap, and Lighthouse leaves it as a manual item, which our schema markup guide covers. Indexing status is the second, because only Search Console shows whether Google indexed a page.

Our take, to close the loop on the launch mistake from the start: the audits earn their keep on the day a template changes. Run them then, fix the failures at the source, and once the ten audits pass, put the hours into the content, links, and real user experience that Lighthouse was never built to measure.

Frequently asked questions about the Lighthouse SEO score

What is a good Lighthouse SEO score?

Aim for every applicable audit to pass, which usually means 100. A score in the low 90s means one ordinary audit failed, such as a missing meta description. A score near 69 often means the page is blocked from indexing, because that audit alone carries about a third of the weight. Read the failing audit before you judge the number, because a 69 can mean the page is invisible in search.

Why is my score different in PageSpeed Insights?

Both tools run the same SEO audits, so differences usually come from the page itself. A tester may see a different version of the page, for example after a consent banner, a redirect, or a login wall, and server errors on robots.txt can come and go. Check which audit changed between the two reports, then test the URL again to rule out a cached or personalized response from your own server.

Does the score affect Google rankings?

Not directly. Google uses Core Web Vitals from real users in its ranking systems, and its page experience guidance says chasing a perfect score just for SEO may not be the best use of your time. What the SEO audits catch can still hurt rankings, though, because a page that is blocked from indexing or returns an error code will not rank, whatever else it does well, so fix those failures first.

How long does it take to fix a Lighthouse SEO audit?

Most fixes are small template edits. Adding a missing meta description, changing generic anchor text, or removing a leftover block can ship in one release, while header blocks and robots.txt server errors take longer because they live in server or CDN settings. The audit updates as soon as you rerun it, but Google's view of the page only changes after it crawls the page again, and that timing is up to Google.

Can a page score 100 and still not be indexed?

Yes. Lighthouse checks whether a page allows indexing, not whether Google indexed it. A page with a perfect score can still be crawled and left out, discovered but never crawled, or folded into a duplicate of another URL on the same site. Check the URL Inspection tool in Search Console for the real status, and read our currently not indexed guide for the common reasons a clean page stays out of the index.

Which Lighthouse SEO audits were removed?

Lighthouse 12 removed the plugins audit, replaced tap targets with an accessibility audit, and moved viewport and font size to Best Practices, and Lighthouse 13 then removed the font size audit entirely. If a guide still lists any of those under SEO, it was written before April 2024. The current scored list has ten audits: indexing, status code, crawlable links, robots.txt, title, meta description, link text, image alt, hreflang, and canonical.

Do I need hreflang and canonical tags to score 100?

No. A page with no canonical tag is marked not applicable, and a page with no hreflang links passes that audit, so leaving them out does not lower the score. Both audits only fail when the tags are present and broken, which makes the score blind to sites that need these tags but lack them. A shop with filtered URLs or a multilingual site should add them for search reasons anyway.

Is Lighthouse the same as a full SEO audit?

No. Lighthouse checks one page against ten technical rules, while a full audit covers the whole site, including crawl paths, indexing status, duplicate content, internal links, backlinks, content quality, and real user speed. Lighthouse is one useful tool inside that larger process. Use it to catch template mistakes fast, then use a crawler, Search Console, and manual review for everything else, because a clean report starts the deeper audit rather than ending it.