Core Web Vitals Green But Rankings Still Dropping

All-green Core Web Vitals and falling rankings isn’t a contradiction; it is a clue. Passing Core Web Vitals is one input among others, and Google says good Core Web Vitals results don’t guarantee top rankings. When positions slide while every metric stays green, look at content relevance, depth and, on sensitive topics, who stands behind the page. The tell is where the decline concentrates: a loss in one section while the rest holds points to content, and more performance tuning is unlikely to touch it.

What Google says Core Web Vitals do

Google’s page experience documentation says Core Web Vitals are used by its ranking systems, and adds two limits. Good results in reports like Search Console’s Core Web Vitals report don’t guarantee that pages will rank at the top of search results, and beyond Core Web Vitals, other page experience aspects don’t directly help a site rank higher. The thresholds, from web.dev’s Web Vitals overview, are LCP within 2.5 seconds, INP of 200 milliseconds or less, and CLS of 0.1 or less, measured at the 75th percentile of page loads.

The implication: if your content is a clear step behind what now ranks, speed doesn’t close the gap. Spending two quarters shaving milliseconds off an already-green page aims effort at an input that isn’t the bottleneck.

Where the decline lives

Before touching anything, map where the loss is. Segment the decline by section in Search Console:

• A uniform drop across the site points to something systemic: a technical problem or a broad reassessment of the site.
• A drop concentrated in one section while others hold points to content. If the blog is falling while product and service pages are stable, the place to look is the blog’s content, not the site’s speed.

This segmentation is the step that can get skipped when a team fixes on Core Web Vitals. The metric is visible and fixable, so it becomes the assumed cause. Core Web Vitals are legible, with a pass or fail, a color, a number and a list of fixes, while a content or authorship gap is fuzzy and uncomfortable to face. The problem with a dashboard is the easier one to pick. The discipline is not to treat the most measurable thing as the most important one, and to let the decline pattern decide where the work goes.

The bar may have moved

A page that earned its ranking years ago against the content that existed then is now compared with everything published since. The results for that search may have been re-contested, and the winners may cover the topic more completely, more currently and with clearer authorship than your page did when it first ranked.

Test it directly. Put your most-declined page next to the top three results for its main search and inventory what each one covers:

• The questions the winners answer that yours doesn’t.
• Worked examples or data points you omitted.
• Recent developments you never added.
• Each page’s publish or last-updated date. If they were refreshed in the past year and yours hasn’t been touched since it first ranked, freshness may explain part of the slide.

The output is a concrete list of gaps, not a vague sense that the competition improved, and that list is what you act on.

Who stands behind the page, on YMYL topics

For finance, health, legal and other “Your Money or Your Life” topics, the question of who wrote the page carries more weight. Google’s guidance on helpful, people-first content says E-E-A-T itself isn’t a specific ranking factor, but that its systems give even more weight to content that aligns with strong E-E-A-T on topics that could significantly affect people’s health, financial stability or safety.

A page bylined to a faceless company name, or to no one, gives readers less to trust than one written by a credentialed, identifiable author with a real bio and a record on the subject. If your declining YMYL pages carry a generic byline while the pages overtaking them carry named experts, fix that first. It isn’t something Core Web Vitals or word count addresses.

Fix in order: identity, then depth, then features

Order matters, because the foundation affects everything above it. On YMYL pages, establish author identity and credentials first; depth published under an anonymous byline can struggle to earn trust on sensitive topics. With identity in place, rebuild depth on the pages that lost the most, covering what the current winners cover rather than chasing a word count. Interactive features and smaller enhancements come last.

Triage by business value, not by ease. The page that lost the most traffic and matters most to revenue gets the first renovation, not the page that is quickest to edit.

Frame the earlier speed work honestly. It wasn’t wasted; green Core Web Vitals remain useful to maintain. The error was sequencing performance work ahead of the diagnosis that could have revealed a content and authorship gap. Calling it a misallocation rather than waste keeps the lesson clear: find where the decline concentrates before committing a quarter of engineering time to the metric that happened to be visible.

What to do

1. Stop treating Core Web Vitals as the lever once they are green.
2. Map which sections and pages declined in Search Console.
3. Compare the worst-losing pages head to head with what now ranks, to find the depth, freshness or authorship gap.
4. On YMYL pages, fix author identity and credentials first.
5. Rebuild depth where the business value justifies it, prioritized by traffic lost.

Recovery, if it comes, follows the content improving relative to the competition, not a date on the calendar.

Frequently asked questions

If Core Web Vitals don’t move rankings much, should I ignore them?

No. Google says Core Web Vitals are used by its ranking systems, so keep them green. The point is sequencing: once they are green, look to content and authorship for the next gains, since Google says good results don’t guarantee top rankings. Treat Core Web Vitals as maintenance, not the lever for recovering lost positions.

How do I tell a content decline from a technical one?

Look at the shape of the loss. A drop concentrated in one section while others hold points to content; a uniform drop across the site points to something systemic or technical. Then compare the worst-losing pages with what now ranks to confirm whether the gap is depth, freshness or authorship rather than crawling or rendering.