llms.txt for WordPress: What Agencies Should Know
What is llms.txt, and should your agency add it to client sites? A practical guide to llms.txt for WordPress: setup in Yoast or Rank Math, honest limits, and how to package it in care plans.
If some of your client sites still run on PHP 8.2, the clock is ticking. PHP 8.2 end of life is December 31, 2026. After that date, the PHP project stops shipping security fixes for the 8.2 branch, and any new vulnerability found in it stays open on every server that has not moved on.
For an agency, this is not a one-site problem. It is a portfolio problem: dozens of client sites, mixed hosts, older themes and plugins, and only a few weeks of runway, right through the holiday season. This guide explains what the deadline means, which PHP version to move to, and a practical plan to upgrade client sites without breaking them or burning your team’s margin.
According to the official PHP supported versions page, PHP 8.2 was first released on December 8, 2022. Its active support ended on December 31, 2024, and its security support ends on December 31, 2026. From January 1, 2027, PHP 8.2 is end of life (EOL).
Here is how the currently supported PHP branches line up, based on php.net:
| PHP branch | Initial release | Active support until | Security support until |
|---|---|---|---|
| 8.2 | Dec 8, 2022 | Dec 31, 2024 | Dec 31, 2026 |
| 8.3 | Nov 23, 2023 | Dec 31, 2025 | Dec 31, 2027 |
| 8.4 | Nov 21, 2024 | Dec 31, 2026 | Dec 31, 2028 |
| 8.5 | Nov 20, 2025 | Dec 31, 2027 | Dec 31, 2029 |
| 8.6 | Nov 19, 2026 | Dec 31, 2028 | Dec 31, 2030 |
Each PHP branch gets two years of active support (bug and security fixes), then two more years of critical security fixes only. Once those four years are up, the branch gets nothing at all.
A site does not stop working on January 1. That is exactly why EOL deadlines get ignored. What changes is the risk:
For your agency, an unplanned PHP switch means emergency tickets, unbilled hours and nervous clients. A planned upgrade is a scoped, billable project that shows clients you are looking ahead for them.
WordPress.org’s official requirements page recommends PHP 8.3 or greater. WordPress still runs on PHP 7.4+, but the same page warns that older versions have reached end of life and may expose a site to security vulnerabilities.
The core team’s PHP compatibility table shows that WordPress 7.0 and 7.1 support PHP 7.4 through 8.5. In practice, that leaves agencies with a simple choice:
Remember that core support is only part of the story. A site is only as compatible as its oldest custom plugin or unmaintained theme.
The goal is to move every client site to a supported version before December 31, 2026, with no surprises. Here is a plan you can run across a portfolio.
Start with a list: client, host, current PHP version, WordPress version, theme, page builder and key plugins. WordPress shows the PHP version under Tools → Site Health → Info → Server, and most management dashboards can report it in bulk. Flag every site on 8.2 or older.
Sort the list into three groups:
Do green sites first to build momentum, and give amber and red sites a proper staging pass.
Run a static check before anything goes live. The open-source PHPCompatibilityWP ruleset for PHP_CodeSniffer flags code that will break or warn on newer PHP versions, and it accounts for the polyfills WordPress core already provides. Read the official PHP 8.3 migration guide for the backward-incompatible changes, and check each premium plugin’s changelog for its tested PHP versions.
Clone the site to staging, switch it to the target PHP version and click through what matters to the client: forms, checkout, logins, search, booking flows and anything with custom code. Turn on debug logging and watch for deprecation notices and fatal errors. Deprecation notices are not urgent today, but they tell you what will break on the next upgrade.
Take a fresh, restorable backup. Switch PHP on production in a low-traffic window, clear caches, then repeat your smoke tests. Keep the old version selectable for a short rollback window if the host allows it, and check error logs again the next day.
Send a short note: what was upgraded, why it mattered, what was tested and when the next deadline is (PHP 8.3 reaches end of life at the end of 2027). This turns invisible maintenance into visible value, and it sets up the next renewal conversation.
Most clean, current WordPress sites move from 8.2 to 8.3 or 8.4 without drama. Trouble usually comes from:
When you find one of these, you have three options: update it, replace it, or rebuild that part of the site. Each is a scoped piece of work the client should approve, not something your team absorbs for free.
A hard deadline across a whole portfolio can swamp a small delivery team in December. It does not have to:
This is where a partner protects your margin. Instead of pulling senior developers off billable projects to debug a ten-year-old plugin, you hand the upgrade queue to a team that does this every week, and you keep the client-facing credit.
Want the same discipline on every handover? Pair this with our website launch checklist for agencies.
PHP 8.2 reaches end of life on December 31, 2026, according to php.net. After that date, the PHP project releases no more security fixes for the 8.2 branch.
No. The site keeps running, but it runs on software that no longer gets security patches. Over time, plugins and themes also stop supporting it, and hosts may move or charge for accounts on EOL versions.
WordPress.org recommends PHP 8.3 or greater. WordPress 7.0 and 7.1 support PHP 7.4 through 8.5, but older versions are end of life and not recommended.
PHP 8.3 is the safer jump for older or plugin-heavy sites and is supported until the end of 2027. PHP 8.4 gives you security support until the end of 2028 and suits well-maintained sites with current plugins. Test on staging either way.
In the WordPress admin, go to Tools → Site Health → Info and open the Server section. Your hosting control panel and most site management tools also show it.
Yes. A white label web development partner can audit, test and upgrade client sites under your agency’s brand, so your clients see your name and your team stays focused on sales and strategy.
Lines + Pixels works as a behind-the-scenes development team for agencies. We can audit your client portfolio, test every site on staging and move them to a supported PHP version, all under your brand. If you are planning bigger changes for 2027, our guide to enterprise WordPress development covers how we approach larger builds.
Book a partner call and let’s plan your PHP upgrades together.

L + P
admin@linesandpixels.team
What is llms.txt, and should your agency add it to client sites? A practical guide to llms.txt for WordPress: setup in Yoast or Rank Math, honest limits, and how to package it in care plans.
Thinking about how to hire a dedicated WordPress developer for your agency? Compare freelance, in-house and white label models, see what to check before you sign, and learn how to keep margins healthy.
What enterprise WordPress development involves, what big clients expect from an agency, and how a white label team helps you deliver it while protecting your margins.
Elevate your business with a custom-designed website that captivates and converts. Let our expert team craft a digital experience perfectly tailored to your brand's needs.