Table of contents10
Last spring a client called me in a panic. Her online shop, the one I had maintained for six years, had stopped taking orders overnight. Nothing had been updated, nothing had been changed — at least, not by her. What had changed was everything around her: her theme’s page builder had quietly dropped support for the newest WordPress, her host had moved her to PHP 8.3, and the search traffic she depended on had shifted to competitors whose sites loaded twice as fast. She had done nothing wrong. She had just stood still while the ground moved.
I am Tom Baker, and I have maintained WordPress sites for clients for over eleven years. I have watched trends come and go — most of them noise. But every few years the ground genuinely moves, and 2026 is one of those years. If you run a WordPress site, freelance for clients, or build sites for a living, seven real shifts are deciding which sites thrive and which ones quietly rot.
Here’s the deal: this is not a prediction list. For each of the seven trends I will tell you what changed, why it matters to your site specifically, and the one concrete thing to do about it this week. Whether you own one small blog or maintain thirty client sites, you will finish this guide with a real action list. Let’s get into it.

One honest note before we start: I am not a futurist and I won’t pretend to see 2030. Everything below is already visible in the WordPress you can download today — in release notes, in the official roadmap at wordpress.org, and in the problems landing on my desk every month. Trends you can act on beat predictions you can’t.
Here is what this guide covers:
- Trend 1: The Block Editor Grew Up — Build Where WordPress Is Going
- Trend 2: AI Moved Into Your Workflow — Use It Without Trusting It
- Trend 3: Speed Became the Price of Admission — Measure, Then Fix
- Trend 4: Attacks Got Faster and Meaner — Your Update Discipline Is the Defence
- Trend 5: Accessibility Became a Legal Question — Fix the Basics First
- Trend 6: “Update and Hope” Died — Staging-First Is the New Normal
- Trend 7: Content Is a System Now — Stop Building Pages, Start Building Patterns
- Frequently Asked Questions
- Final Thoughts
Ready? Let’s get started.
Trend 1: The Block Editor Grew Up — Build Where WordPress Is Going
I remember the first time a client asked me to “just move the header a bit” on a block theme, back when full-site editing was new and rough. I broke the layout three times before lunch. Last month I did the same job in eleven minutes, in the browser, with no code at all — and the client watched me do it over a screen share. That is how far the block editor has come.
Here is what changed: the Site Editor is no longer the experimental side of WordPress. It is the normal way new sites get built and old sites get redesigned. Block themes, patterns, and the style system have matured to the point where whole headers, footers, templates, and landing pages are assembled from blocks — and the official WordPress roadmap keeps pushing this direction with every release. If you are still building everything with shortcodes and widget areas, you are building on yesterday’s foundation.
Why does this matter for your site? Two reasons. First, compatibility follows the crowd: plugin and theme developers now target the block editor first, so classic-only setups get fewer new features and slower bug fixes. Second, hiring and help get easier: every tutorial, freelancer, and support answer in 2026 assumes the block editor. The longer you wait, the more translation you do in your head.
Now, the action — and do this on a staging copy, never live. Open the Site Editor (Appearance → Editor) and rebuild one small thing you currently maintain with code or a page builder: a footer, a call-to-action section, a simple landing template. Save it as a pattern (the three-dot menu → “Create pattern”) so you can reuse it. Time yourself. If it felt faster than your old way, you have your answer about where your next project should be built. If your site runs a classic theme, you don’t need to switch today — but your next redesign should start with a block theme, full stop. The ground has moved; plant your feet on the new side.
Trend 2: AI Moved Into Your Workflow — Use It Without Trusting It
A fellow freelancer showed me his new “process” in June: he pastes a client brief into an AI chat, gets a full homepage draft, drops it into WordPress, and ships it. It looked miraculous. Then I read the draft. The pricing table was wrong, the testimonial names were invented, and one paragraph described services the client doesn’t offer. He had shipped fiction with a beautiful layout.
WordPress itself is moving in this direction — version 7.0 introduced an AI Client with an Abilities API, and the official roadmap keeps AI-assisted workflows on the agenda. Hosting companies, SEO tools, and page builders all ship AI features now. The trend is real and it is not going away. But here is the line I draw after eleven years of cleaning up messes: AI is a junior assistant, not a colleague. It drafts; you decide.
What this means for you is practical, not philosophical. Use AI for the parts where mistakes are cheap and visible: first drafts of blog outlines, alt-text suggestions, ten headline options, summarising long support threads. Never let it touch the parts where mistakes are expensive and invisible: prices, legal pages, contact details, medical or financial claims, anything published without your eyes on every word. The clients who thrive in 2026 are not the ones avoiding AI or the ones worshipping it — they are the ones with a review step between the AI and the publish button.
Your action this week: pick one repetitive task — say, writing meta descriptions — and let an AI tool draft ten of them. Then read every single one before using it. Notice what it gets wrong. That gap, between draft and publish-ready, is your job security. Build your workflow around it: AI drafts, human approves, WordPress publishes. The trend rewards the careful, not the fast.
Trend 3: Speed Became the Price of Admission — Measure, Then Fix
I ran a speed test on a client’s site in March: 6.4 seconds to interactive on a phone. She told me her bounce rate was “fine.” It wasn’t — her analytics showed 68% of mobile visitors leaving before the page finished loading. We got the site to 2.1 seconds. Same content, same design. Her enquiries doubled in six weeks. I have seen this exact story play out a dozen times, and it never stops being dramatic.
Speed is no longer a nice-to-have or a geek’s hobby. It is the price of admission. Search engines have measured page experience for years, visitors have zero patience left, and the tooling to fix slow sites has never been better. The uncomfortable truth: most slow WordPress sites are slow because of decisions, not technology — a bloated theme, twenty plugins where five would do, uncompressed images, no caching. All fixable, all owned by you.
So here is your action, and it starts with a number, not a plugin. Test your homepage on a real speed tool today and write down three numbers: how fast the biggest content appears, how fast the page responds to input, and how much the layout jumps around while loading. Then fix the biggest offender first — it is almost always images or too many plugins. Compress every image before uploading (your media library will thank you), delete plugins you haven’t used in months, and turn on page caching if your host offers it. Measure again. That before-and-after pair is worth more than any optimisation plugin’s marketing page. If you want the full walkthrough, our Core Web Vitals guide breaks each metric into plain English.
The trend is simple: fast sites get the traffic, slow sites get the excuses. Pick which side you’re on, then measure your way there.
Trend 4: Attacks Got Faster and Meaner — Your Update Discipline Is the Defence
The call I dread came at 11pm last October: “Tom, our site is sending spam to our customers.” A client’s brochure site — twelve pages, nothing fancy — had been infected through a contact-form plugin that was four versions behind. The attackers didn’t target her. They target everyone, automatically, all the time, and they walk through whichever door was left open. Hers was a plugin update she had been “meaning to do.”
This is the trend nobody wants to hear: attacks on WordPress sites are increasingly automated and fast. Security researchers keep reporting the same pattern — vulnerabilities in popular plugins get exploited within hours of disclosure, and supply-chain style attacks (one compromised component infecting thousands of sites) are now a regular headline. Your site doesn’t need to be important to be attacked. It just needs to be reachable.
But here is the good news, and I mean it: the defence hasn’t changed, only the urgency has. The sites that get hacked in 2026 are overwhelmingly the ones running outdated software. The fix is boring and it works: update WordPress core, themes, and plugins promptly; delete what you don’t use (inactive plugins are still doors); use strong unique passwords with two-factor authentication; keep real backups you have actually tested. That last one matters more than people think — read our 3-2-1 backup strategy guide before you need it, not after.
Your action this week takes twenty minutes. Log in, go to Dashboard → Updates, and update everything. Then go to Plugins → Installed and delete every plugin you can’t name a job for. Then check: does your site have two-factor authentication on admin accounts? If not, add it today. Automated attacks beat lazy defences; disciplined defences beat automated attacks. Be disciplined.
Trend 5: Accessibility Became a Legal Question — Fix the Basics First
A client in e-commerce got a letter last year — the formal kind, from a lawyer — saying her site wasn’t accessible to blind users and she had thirty days to fix it or face a claim. She thought accessibility was something only governments worried about. She learned otherwise, expensively. Enforcement of accessibility rules has been tightening across Europe and beyond, and in 2026 “we didn’t know” is not a defence that impresses anyone.
I am not a lawyer, so treat this as a site owner’s practical view, not legal advice: accessibility is now a business risk, not just a nice value. The good news is that the basics — the things that prevent most complaints — are also the things that make your site better for everyone: readable colour contrast, keyboard-navigable menus, alt text on images, form labels that actually label the fields, headings in logical order.
Your action this week is a twenty-minute audit anyone can do. Unplug your mouse and try to use your site with only the Tab key — can you reach the menu, the forms, the checkout? Then check your body text contrast: light grey text on white backgrounds fails, and it is everywhere. Then run one page through a free contrast checker and fix the failures. These three steps catch the majority of real-world problems. For the deeper work, our accessible forms guide and WCAG basics guide walk through it properly.
The trend here rewards early movers. Fixing accessibility after a complaint costs ten times more than building it in now. And every fix — clearer contrast, better keyboard support — also helps your mobile users, your older users, and your search rankings. It is the rare trend where doing the right thing and the profitable thing are the same thing.
Trend 6: “Update and Hope” Died — Staging-First Is the New Normal
I used to update client sites live on Tuesday mornings, holding my breath, keeping one eye on the clock and one on the error log. It worked — until the Tuesday it didn’t, and a WooCommerce update took a store’s checkout down for four hours during their biggest sale week. I have never updated a live site first since. That Tuesday cost me more in apology emails than a staging site would have cost in a decade.
The trend: professional WordPress work now happens staging-first. A staging site is a private copy of your site where updates get tested before they touch the real thing. Most decent hosts offer one-click staging in 2026 — it is no longer a luxury feature. The workflow is simple: copy live to staging, run all updates on staging, click through the important pages (homepage, checkout, contact form), then push to live. Fifteen extra minutes that prevent the 11pm panic calls.
This pairs with a smarter approach to automatic updates. WordPress can update itself, and for minor security releases it should — those are the urgent ones. For major versions and plugins, the careful move is: automatic for the small stuff, manual-with-testing for the big stuff. Our auto-updates guide lays out the exact tier system I use for clients.
Your action this week: check whether your host offers staging. If it does, make a staging copy today and run your next round of updates there first. If it doesn’t, that tells you something about your host — file it under “reasons to switch at renewal.” And if you ever want to preview what’s coming before it lands, our beta testing guide shows how to test new WordPress versions safely. “Update and hope” was always gambling. In 2026, the house always wins — so stop playing.
Trend 7: Content Is a System Now — Stop Building Pages, Start Building Patterns
The most successful site I maintain publishes forty articles a month with a team of three. Their secret isn’t working harder — it’s that they never build a page from scratch. Every article uses the same block patterns: the same intro layout, the same callout boxes, the same FAQ block, the same author box. A new writer is productive on day one because the system carries the design. Compare that to the sites where every page is a snowflake, hand-built, slightly broken in slightly different ways.
This is the quietest of the seven trends and maybe the most important: winning WordPress sites are built as systems, not pages. Reusable block patterns, a proper heading structure, consistent templates, content that can be translated or repurposed without rebuilding. The block editor made this practical — patterns and reusable blocks mean your tenth landing page costs a tenth of the effort of your first. Sites built as snowflakes get slower, messier, and more expensive with every page. Sites built as systems get faster and cheaper.
Your action this week: pick the three page types you build most — for most sites that’s articles, landing pages, and service pages — and turn each into a saved pattern with your real headings, your real call-to-action blocks, your real FAQ layout. The next time you need one, start from the pattern. It will feel slower the first time and dramatically faster every time after. If you publish internationally, build the pattern translation-ready from day one: short strings, no text baked into images. Future you will be grateful.

What To Do This Week: Your 2026 Action List
Trends are only useful if they change what you do on Monday morning. Here is the whole guide compressed into one checklist, in the order I would do it:
1. Rebuild one section in the Site Editor on staging and save it as a pattern (Trend 1). 2. Set up your AI review step: AI drafts, you approve, WordPress publishes — never the reverse (Trend 2). 3. Measure your speed and fix the single biggest offender, usually images or plugin bloat (Trend 3). 4. Update everything and delete unused plugins, then enable two-factor authentication (Trend 4). 5. Do the keyboard-only test on your site and fix contrast failures (Trend 5). 6. Make a staging copy and run your next updates there first (Trend 6). 7. Turn your three most-built page types into patterns (Trend 7).
Do one a day and you’re done in a week. Do them all and your site is genuinely ahead of most of the WordPress sites on the internet — because most site owners will read trend articles and change nothing.

Frequently Asked Questions
Do I really need to switch to a block theme in 2026? Not overnight, and not if your current theme works well and is actively maintained. But every new project should start with a block theme, and every redesign is a chance to switch. The ecosystem — tutorials, new plugins, support answers — is moving to blocks. Swimming against that current gets harder every year, so plan the move rather than being forced into it.
Is AI content going to get my site penalised? Publishing raw, unreviewed AI text is what gets sites in trouble — thin, generic, sometimes wrong content that readers bounce from. AI-assisted content with real human review, real experience, and real fact-checking is just a faster writing process. The rule is simple: if you wouldn’t sign your name to it after reading it, don’t publish it.
My site is slow but my host says everything is fine. Who is right? You are, if your measurements say so. “Everything is fine” from a host usually means the server is healthy — but your site’s speed is mostly decided by your theme, plugins, and images, not the server. Measure with a real tool, fix your side of the equation first, and only then judge the hosting.
How often should I really update WordPress? Security and minor updates: promptly, ideally automatically. Major versions and plugin updates: within a week or two, tested on staging first. The dangerous pattern isn’t updating too often — it’s updating never, then doing eighteen months of updates at once and wondering why things break.
I run a tiny blog with no shop. Do these trends still apply to me? Yes — arguably more. Big sites have teams; you have you. Systems (patterns), speed (fewer plugins), and discipline (updates, backups) are how a one-person site punches above its weight. Trend 7 alone will save a solo blogger hours every month.

Final Thoughts
Eleven years of maintaining WordPress sites has taught me that the ground moves whether you watch it or not. The clients who sleep well in 2026 won’t be the ones who chased every trend — they’ll be the ones who picked the real shifts and did the boring work: building where WordPress is going, measuring their speed, updating with discipline, testing before publishing, and building pages as systems instead of snowflakes.
My honest line: I can’t predict 2027, and anyone who says they can is selling something. But I can tell you that every item on the checklist above has paid for itself on real client sites, many times over. Start with the one that scared you most while reading — that’s usually the one your site needs first.
Which trend hit closest to home for your site? Drop a comment below — I read every one, and the best questions become future guides. Related reading: is your WordPress theme slowing you down, how to choose a WordPress theme, how to stop WordPress brute-force attacks, WordPress major versus minor updates, and WebP versus AVIF in WordPress in 2026.










