Google Just Killed Its Own AMP Cache — Here’s What Publishers Should Do Now
It’s not a surprise. It’s a relief.
On July 1, Google stopped serving AMP pages from its cache. No more google.com URLs. No more viewer. No more signed exchanges.
Click an AMP result in search now? You land on the publisher’s own AMP page. Full stop.
And honestly? Good riddance.
I’ve watched publishers waste years chasing a ghost — thinking AMP was an SEO advantage, when all it was, was a Google-owned highway with tolls you didn’t know you were paying.
Let me be blunt: AMP didn’t make your site faster.
It made Google’s infrastructure faster.
And you? You got a shiny badge and a broken analytics pipeline.
I’ve seen sites where the AMP version loaded faster — sure. But the original? Slower. Because the CMS was generating two versions. Because the ad tags were duplicated. Because the cache invalidated every time someone changed a headline.
The real cost? The time. The dev hours. The debugging nightmares.
Now? All of that’s gone.
Google didn’t kill AMP because it was broken.
They killed it because you stopped caring if they controlled it.
And that’s the quiet revolution no one’s talking about.
You didn’t need Google to be fast.
You just needed to stop letting them own your tech.
So what do you do now?
First — stop deleting your AMP pages.
Unless they’re actively breaking things, leave them. They still rank. They still get traffic. And if they’re already built? Why tear them down?
But stop thinking of them as an SEO tool.
They’re just a template.
Like a mobile-optimized page. Or a responsive layout.
Your job now? Make sure your AMP host page loads fast.
Not because Google says so.
Because your readers deserve it.
And if you’re still using signed exchanges? Delete them.
They’re gone. Google removed the docs. The validation servers are offline.
Your AMP page doesn’t need a proxy anymore.
It just needs to be served.
And if you’re thinking about switching to a different format?
Go ahead.
But don’t chase the next shiny thing.
Chase your users.
Check your Core Web Vitals.
Fix your ad load.
Optimize your images.
Use a real CDN.
Build your own speed.
Not Google’s.
Yours.
This isn’t the end of AMP.
It’s the end of dependency.
And for the first time in a decade? You’re in control.
So breathe.
And get back to work.
Your readers aren’t waiting for Google.
They’re waiting for you.
The Old Way Was a Trap
Remember how it used to work?
You clicked an AMP result.
You got a page with a google.com URL.
The content? Yours.
The URL? Not yours.
And the analytics? Half-broken.
Because Google was serving the page.
Your tags? Sometimes fired. Sometimes not.
Your revenue? Sometimes tracked. Sometimes ghosted.
And the worst part?
You thought it was normal.
You thought this was the price of being in search.
But here’s the truth:
Google didn’t build AMP to help you.
They built it to keep you.
To keep you on their platform.
To keep you dependent.
To keep you from building your own audience.
They gave you a fast page.
But they took your URL.
Your data.
Your relationship with your readers.
And now? They’re done.
Not because they changed.
Because you did.
Publishers stopped asking, "How do I get Google to like me?"
They started asking, "How do I own my own readers?"
And that’s why this move feels like freedom.
No more Google-hosted URLs.
No more hidden redirects.
No more broken tracking.
Just your page. Your domain. Your control.
It’s not a loss.
It’s a liberation.
What Changed — And Why It Matters
Here’s what Google actually changed on July 1:
- AMP results in search no longer load from the AMP Cache.
- The AMP Viewer is gone. No more google.com URLs.
- Signed exchanges are no longer used or supported.
- Google removed all documentation references to AMP Cache and Viewer from their official AMP docs.
That’s it.
No algorithm update.
No ranking change.
Just a technical shift.
But here’s the kicker:
This wasn’t a technical decision.
It was a political one.
Google realized they couldn’t keep pretending AMP was a "user benefit."
Publishers were leaving.
Ad networks were leaving.
Even Google’s own engineers were whispering that AMP was a dead end.
So they pulled the plug.
Cleanly.
Quietly.
No fanfare.
No press release.
Just a changelog update.
And now?
You’re free.
No more signed exchanges.
No more cache invalidation.
No more waiting for Google to serve your content.
Just your server. Your CDN. Your speed.
And your readers.
They’re the only ones who ever mattered.
The Slow Death of AMP (A Timeline)
This didn’t happen overnight.
It was a slow, painful fade.
2021: Google drops AMP as a requirement for the Top Stories carousel.
The lightning bolt icon? Gone.
Publishers cheered.
Then they kept building AMP anyway.
Because they thought: "Maybe it still helps?"
2022: Google News on mobile starts bypassing AMP URLs.
Traffic to AMP pages? Drops.
Publishers panic.
Then they double down.
Because they don’t know what else to do.
2023: Google removes AMP from the "Best Practices" section of their Search docs.
Still no announcement.
Just a quiet edit.
2024: Google stops serving AMP in the Discover feed.
More traffic drops.
More publishers start asking: "Why are we still doing this?"
2025: Google quietly removes AMP from the "Mobile-Friendly Test" tool.
No warning.
No email.
Just a broken test.
And then — July 1, 2026.
The final nail.
No more cache.
No more viewer.
No more excuses.
You’re not supposed to notice.
But you do.
Because you’ve been waiting for this.
For years.
Ranking? Still the Same.
Let me say this again — because I’ve seen too many publishers panic:
AMP content still ranks just like any other page.
No penalty.
No bonus.
No hidden signal.
Google made this crystal clear.
So if you’re thinking: "Should I delete my AMP pages to improve SEO?"
No.
Don’t.
Unless they’re broken.
Unless they’re slowing you down.
Otherwise? Leave them.
They’re just a page.
Like any other.
Your ranking isn’t tied to AMP.
It’s tied to your content.
Your speed.
Your trust.
Your authority.
And those? They’ve always been yours.
Not Google’s.
What Publishers Should Do Now
So what’s next?
Here’s your checklist — no fluff.
-
Check your AMP pages — Do they load? Do they render? Do they show ads? If yes, leave them.
-
Delete signed exchanges — They’re dead. Your server doesn’t need them anymore. Remove the headers. Kill the configs.
-
Audit your AMP analytics — Are your tags firing? Are you tracking clicks? If not, fix them. Or replace them.
-
Optimize your AMP host page — Speed matters. Not Google’s speed. Yours. Use a CDN. Compress images. Lazy-load ads.
-
Stop thinking of AMP as SEO — It’s not. It’s a format. Like a responsive layout. Treat it like one.
-
If you’re building new content? Skip AMP.
Build a fast, clean, mobile-optimized page.
Use modern HTML.
Use a real CDN.
Use your own analytics.
And if you’re wondering: "What about mobile?"
You don’t need AMP for mobile.
You need good hosting.
You need clean code.
You need speed.
And you’ve had all of that since 2018.
So why did you wait?
Because you trusted Google.
And now?
You don’t have to.
The Real Win Isn’t Speed — It’s Ownership
The end of Google’s AMP cache isn’t about speed.
It’s about ownership.
For ten years, publishers let Google decide how their content was served.
They let Google decide what URLs looked like.
What data got tracked.
What ads showed.
What users saw.
And now?
You get to decide.
Your page.
Your URL.
Your speed.
Your audience.
This isn’t the end of AMP.
It’s the end of dependency.
And the beginning of something better.
You’re not a publisher trying to please Google anymore.
You’re a publisher serving your readers.
And that? That’s the only thing that ever mattered.