Ritner Digital June 2026 SEO Benchmark Report
Part of our ongoing monthly benchmark series. Previously: Ritner Digital 90-Day SEO Report Card, April 2026 Benchmark Report, and May 2026 Benchmark Report.
We've been publishing these benchmark reports for a simple reason: it's easy to tell a client "trust the process" during the slow months, and it's a lot harder — and a lot more honest — to hand them the actual Search Console export while it's happening. April was slow. May was slower, and at points genuinely discouraging. We had days with zero clicks on nearly 2,000 impressions. We had an average position that briefly touched 40. June is the month where the math finally turned in our favor, and unlike a lot of "we turned it around" posts, we can point to almost the exact calendar day it happened and explain, with a source, why.
This report walks through what changed, why we think it changed, which specific pieces of content did the heavy lifting, and — because we said we'd always show our work — where we still don't have a great answer yet.
Look at the shape of that chart, not just the endpoints. There's a long, noisy flat stretch through April and most of May where position bounces between the high teens and high 30s and clicks rarely clear single digits. Then there's a visible pivot right around the start of June, followed by a steady, unbroken climb into July. That shape matters, and we'll get to exactly why in a minute.
The headline number
Domain-wide, June 2026 vs. May 2026, pulled straight from Search Console (Web search type, Jun 1–30 vs. May 1–31):
That mobile line is the one worth sitting with the longest. In May, mobile rankings were nearly 20 spots worse than desktop — a clear sign Google simply hadn't extended us the same trust on mobile yet, even though it was crawling and indexing the mobile version of every page just fine. By June, mobile and desktop had converged almost exactly, landing within a tenth of a point of each other. That's not a metric that moves because someone tightened up a meta description or added an FAQ schema block. That's a domain-wide trust signal catching up across device types at roughly the same moment — which is exactly the kind of movement you'd expect from an index-wide re-scoring event rather than a page-by-page fix.
The story of the month: this wasn't organic drift, it was a core update
We didn't want to write "rankings just started improving, must be all our hard work" without actually checking whether something external happened, so we checked. On May 21, 2026, Google began rolling out its May 2026 broad core update — the second core update of the year, following the March 2026 core update — and it finished rolling out on June 2, 2026, taking a little under twelve days. Google's own framing, as always, was intentionally vague: "This is a regular update designed to better surface relevant, satisfying content for searchers from all types of sites."
Line up our daily data against that specific window and the timing is hard to write off as coincidence:
April 3 through roughly May 18: average position bounces around in a wide band — mostly high teens to high 20s, with a brief dip into the low 40s. Impressions are climbing steadily (a good sign — Google is crawling and indexing more of the site) but clicks stay stubbornly low, including multiple days at 0–2 clicks on well over 1,000 impressions. This is the textbook profile of a new domain sitting outside the "trusted enough to click" tier: Google knows the pages exist, is willing to show them, but isn't ranking them high enough for anyone to actually land on them.
May 19–31 (the volatile stretch right before and during rollout): things got noticeably worse before they got better. Position spiked to 40.4 on May 20, and we saw a string of high-30s days through May 23–28. This is normal and expected — Google has published guidance that rankings are unstable during a core update rollout and specifically advises waiting at least a full week after a rollout completes before drawing any conclusions from the data, because the update itself is still being applied unevenly across the index in the meantime.
June 2 (rollout complete) forward: a clean, sustained climb. Average position went from 33.0 on June 1 down to 25.2 by June 6, cracked 20 for the first time in over a month on June 9 (18.3), and settled into a 14–18 range for essentially the entire back half of June, closing the reporting window at 14.1 on July 2. Clicks tell the same story in reverse — from single digits most days in May to a consistent 15–31 per day by late June, with several 20+ days in a row by the final week of the month.
We're not claiming the core update personally rescued our website — Google has been explicit for years that core updates re-score the entire index against a broad quality model rather than targeting individual sites, positively or negatively. What we think actually happened is a lot less magical and, frankly, more useful for planning purposes: this domain was already sitting in the slow, months-long trust-accumulation window that every new site goes through — the same window we described in detail in our 90-day report card — and the core update landed at the exact moment that accumulated trust was ready to convert into visible ranking movement. The update didn't build the trust. It re-sorted the index and let the trust we'd already built actually show up in the rankings.
That distinction matters if you're a client reading this and wondering whether you should "wait for the next core update" as a strategy. You shouldn't. You should keep doing the unglamorous work — publishing specific, well-structured, genuinely useful content — so that whenever the next re-sort happens, whether it's a named core update or one of the smaller, unannounced tweaks Google ships continuously, you're positioned to benefit from it instead of getting flattened by it.
The content that actually moved the needle
Aggregate numbers make a good headline, but the query-level and page-level data tell you why the aggregate moved. Two brand-new posts did most of the work in June, and — this is the interesting part — neither one had a single click or impression in May. Both were entirely new content that happened to land right as the index was being re-sorted.
The "Freddy the German tourist" piece is the one we keep coming back to internally, because it didn't just perform in search — it visibly changed our geographic mix for the month. Queries like "german tourist freddy," "freddy tourist," "freddy german tourist," and "freddy the german tourist" all showed up in our top-queries report for the very first time in June, all pointing at that single post, and Germany's country-level numbers moved right alongside them.
Germany's average position improvement — 16.58 down to 9.46 — was the single largest positional gain of any country we track this month, and it's not a coincidence that it happened the same month we published a piece with "German tourist" sitting right in the title. Netherlands is worth a footnote too: clicks stayed flat at 8, but impressions there jumped from 653 to 4,137 and position nearly doubled from 17.51 to 8.9, which tells us Google is now surfacing us for a much wider set of Dutch queries even though searchers haven't fully started clicking yet. That's often what the month before a click breakout looks like.
The bigger lesson we keep repeating to clients: writing toward a specific, searchable hook — a name, a place, a real, current query someone would actually type into Google — does more for international reach than a generic "we do global SEO" service page ever will. Nobody searches "global SEO agency." Plenty of people, apparently, search "freddy the german tourist."
The engagement layer: what GA4 says about the same posts
Search Console tells you whether people found the page. GA4 tells you what they did once they got there, and June's winners held up well on that front too. The Freddy post pulled 216 sessions and 194 new users in June, with an average engagement time of 41.5 seconds — long enough to suggest people were actually reading the piece rather than bouncing straight off the headline. "Did Claude Get Worse at Writing?" converted at nearly 24% on our key-event tracking (31 key events across 125 sessions), which is one of the stronger conversion rates on the entire site this month, new post or old.
That combination — strong Search Console numbers and strong engagement numbers on the same pages — is the thing we actually care about. It's possible to rank well and still have people leave in three seconds because the content doesn't deliver on the title. That's not what happened here. Both breakout posts held attention roughly in line with, or ahead of, our site average, which tells us the ranking gains weren't propped up by a clickbait title with nothing behind it.
Our blog index page (/blog) also deserves a mention here, even though it's not a "content" page in the traditional sense: it went from 59 sessions in May to 1,653 sessions in June. Some of that is direct navigation from people who landed on a post and then browsed further, and some of it is simply a reflection of the same overall traffic lift showing up in internal navigation. Either way, it's a good sign that people who arrive via one of the breakout posts are sticking around the site rather than reading one page and leaving.
Devices: the mobile catch-up, in more detail
We flagged the mobile numbers above but they deserve a closer look, because this is the clearest "trust, not tactics" signal in the entire dataset.
Mobile clicks grew 457% month over month — more than double the growth rate of desktop's already-strong 158% — and mobile CTR nearly doubled on top of that, from 0.47% to 0.93%. We shipped no mobile-specific redesign work in June, no Core Web Vitals overhaul, nothing that would explain a device-specific improvement on its own. What we think we're actually seeing is Google's index-wide trust score catching up to parity across devices at the same moment the broader core update settled, which lines up cleanly with the pattern in the daily chart above. Tablet numbers remain tiny in absolute terms (4 clicks is still 4 clicks), but even there, position improved by more than 22 points — the largest single positional swing of any device segment we track.
Comparing three months side by side
It's worth stepping back and looking at April, May, and June together, because the three-month arc tells a cleaner story than any single month does on its own.
April was almost entirely an impressions story. Clicks stayed low and flat, but impressions climbed steadily across the month, which told us Google was expanding how much of the site it was willing to show — just not yet willing to rank it high enough to earn clicks.
May was the frustrating middle month. Impressions kept growing, sometimes sharply (multiple days over 3,000 impressions by mid-May), but average position got worse before it got better, dropping into the high 30s and briefly touching 40.4 on May 20. If you'd only looked at position in isolation during that window, it would have looked like regression. In hindsight, it was the volatile lead-up to a core update rollout that was about to work in our favor.
June is where impressions, position, and clicks all finally moved in the same direction at the same time. That alignment — all three metrics improving together, rather than one improving while another stalls — is usually the strongest signal that something structural changed, as opposed to a single lucky post having a good week.
What this means going into July
A few honest takeaways, in the same spirit of transparency we tried to bring to the April and May reports:
The timing was mostly out of our hands. A core update landing during our trust-accumulation window is good luck as much as it's good strategy. What was in our control was having genuinely new, specific, well-built content ready to be re-indexed the moment the update settled — the Freddy piece and the two Claude pieces weren't evergreen filler sitting around waiting for a boost, they were built around real, current queries people were actively typing into Google.
New-domain SEO is still mostly a waiting game, until suddenly it isn't. The April-through-mid-May stretch of near-zero clicks on tens of thousands of impressions is exactly the pattern we described in our 90-day report card, and it doesn't feel like progress while you're living through it. It is progress. The impressions climbing steadily while clicks stayed flat was the leading indicator the whole time.
Specificity travels internationally better than "global" content does. The Germany numbers are the clearest proof of that we've had all year, and the Netherlands impressions spike suggests a second country might be about to follow the same pattern.
We're not declaring permanent victory. Google's own guidance is to wait a full post-rollout week before drawing conclusions, and we're now well past that. The trend line through July 2 looks like a genuine new baseline rather than rollout noise — but we'll be watching July closely before we start treating "mid-teens average position" as the normal state of this domain rather than a high point.
We're going to lean harder into specific, timely hooks. If a post about a viral German tourist named Freddy outperformed several evergreen service-page-adjacent posts this month, that's not a fluke we ignore — it's a content strategy signal we're going to keep testing deliberately rather than treating as a one-off.
We'll be back with the July numbers, and — pending anything else that ships between now and then — we're expecting to talk more about how content built around live, specific, timely hooks keeps outperforming the evergreen stuff on this particular domain.
Methodology note: all Search Console figures reflect Web search type only, exported for the periods May 1–31, 2026 and June 1–30, 2026, plus a daily trend spanning April 3–July 2, 2026, unless otherwise noted. GA4 figures reflect All Users for the same monthly date ranges. Core update timeline sourced from Google's Search Status Dashboard and Search Engine Land's coverage of the May 2026 broad core update rollout.
Want a benchmark report like this for your own site? If you're staring at your own Search Console data trying to figure out whether a dip — or a jump — is something you did or something Google did, get in touch with us and we'll help you find out.
Frequently Asked Questions
Why did our Google rankings suddenly improve in June 2026?
The most likely explanation is Google's May 2026 broad core update, which rolled out from May 21 to June 2, 2026. Core updates re-score the entire search index against a broad quality model rather than targeting individual sites, positively or negatively. In our case, the domain had spent April and most of May in a slow trust-accumulation period — lots of impressions, very few clicks — and the core update appears to have landed at the moment that accumulated trust was ready to convert into visible ranking movement. Average position dropped from the 30s in late May to the mid-teens by early July, and clicks roughly tripled in the same window.
What is a Google core update, and how is it different from other algorithm changes?
A core update is a broad, significant change to Google's search ranking systems, announced publicly because of how widely it can affect sites across the web. Google has said core updates are designed to "better surface relevant, satisfying content for searchers from all types of sites" rather than targeting specific pages or sites directly. This is different from smaller, unannounced tweaks Google ships continuously, which are narrower in scope and rarely produce the kind of visible, domain-wide shift we saw in June.
How long does it take to see the effects of a core update?
Google's own guidance is to wait at least a full week after a core update finishes rolling out before drawing conclusions, since rankings are unstable during the rollout itself. The May 2026 core update completed on June 2, 2026, and in our data the clearest, most consistent gains didn't stabilize until roughly a week later — average position kept improving steadily through the rest of June rather than jumping immediately on June 2.
Why did our mobile rankings improve more than desktop?
Mobile clicks grew 457% month over month compared to 158% on desktop, and mobile average position improved by more than 16 spots (35.55 to 19.09) versus about 5 spots on desktop. We didn't make any mobile-specific changes to the site in June. The most likely explanation is that Google's trust in the domain caught up across device types at roughly the same time, which is consistent with an index-wide re-scoring event rather than a page-level fix.
Does publishing content about specific, timely topics actually help SEO more than general service content?
In our June data, yes, noticeably. Two brand-new, highly specific posts — one built around a real, current event and another responding to an active industry conversation — accounted for a large share of the month's click and impression growth, and neither had any search visibility the month before. One of those posts also drove a measurable jump in traffic and average position from Germany specifically, tied directly to queries that only made sense once that content existed. Specific, well-timed content tends to give search engines a much clearer, more searchable hook than broad, evergreen service pages do.
How often will Ritner Digital publish these benchmark reports?
Monthly. This report follows our April and May benchmark reports, as well as our 90-day report card. We publish the real numbers, including the months that don't look great, because that's the only way a benchmark report is actually useful to anyone reading it.
Want a benchmark report like this for your own site? If you're staring at your own Search Console data trying to figure out whether a dip — or a jump — is something you did or something Google did, get in touch with us and we'll help you find out.