WordPress 7.1 is due on 19 August 2026 and changes the HTML structure of the admin post list tables, according to a Search Engine Journal report published on 6 August 2026. The checkbox column converts from a <th> to a <td>, the post title column moves from a <td> to a <th scope="row">, the title row header gains an aria-label carrying the post title, and responsive collapsed cells are updated to use a flex layout. Plugins and admin customisations that target specific <th> and <td> elements with CSS or JavaScript selectors risk breaking. Public-facing website content is unaffected.
What the WordPress 7.1 change fixes
The rewrite closes an 11-year-old accessibility bug. In the current markup, screen readers announce "Select All" instead of the post title when moving through a list table row, which leaves anyone using assistive technology without the one piece of information that identifies the row. Swapping the row header to the title column fixes that announcement.
The reasoning quoted in the report is that a row header should be "the cell with the main object the table refers to", meaning the post title, the plugin name, and so on, rather than a checkbox that says the same thing on every row.
What changes in the markup on 19 August 2026
The table below lists the four structural changes described in the Search Engine Journal report of 6 August 2026.
| Element | Before 7.1 | In WordPress 7.1 |
|---|---|---|
| Checkbox column | <th> | <td> |
| Post title column | <td> | <th scope="row"> |
| Screen reader announcement | Announces "Select All" | aria-label carries the post title |
| Responsive collapsed cells | Existing collapsed-cell layout | Flex layout |
Who is actually at risk
Anything that reaches into a list table by element type is exposed. That covers custom admin columns, bulk-edit tooling, client dashboards, and any CSS written against the old cell structure to restyle the posts screen. A selector written as a table cell in position two stops matching when position two changes element type.
Search Engine Journal reported that a code review indicated the major SEO plugins, Yoast SEO, Rank Math and All in One SEO, are likely to remain compatible. Likely is not confirmed, and the report advises checking changelogs before upgrading rather than treating that review as a guarantee.
This is a wp-admin change, not a ranking change
Public-facing content is untouched. Nothing in this release alters what a visitor or a crawler sees on a live page, so the exposure is to internal workflows and editorial tooling. If an editorial team relies on a custom column showing word count, review status or a client approval flag, that column is the thing to test.
The distinction matters because the release notes will circulate with the words accessibility and breaking change next to each other, which tends to trigger a panic about search visibility that this change does not warrant.
What this means for Thai marketers
WordPress runs a large share of Thai business and agency sites, and custom admin columns and client-facing dashboards are common on them. The cheap precaution is to stage the 7.1 upgrade on a copy before 19 August 2026 and open the Posts and Pages screens, rather than finding out on a live editorial site.
A short pass covers it. Load a staging copy, check every admin screen a client or editor touches daily, read the changelog of any plugin that adds columns to those screens, and note anything custom that was written years ago by someone no longer on the project. Teams maintaining WordPress builds for clients should run this before the release rather than after, and anyone whose SEO workflow depends on those admin columns has the same deadline. If a site has not had a technical review in a while, an upgrade window is a reasonable moment to schedule one.
FAQ
Will WordPress 7.1 hurt my rankings?
No. The change affects the wp-admin post list tables only, and Search Engine Journal reported explicitly that public-facing website content is unaffected. What visitors and crawlers see on the live site does not change.
Do I have to do anything before 19 August 2026?
Only if your site uses custom admin columns, admin CSS or JavaScript that targets list table cells. Sites running stock WordPress with mainstream plugins have nothing to prepare, though staging the update first is still the safer habit.
Will Yoast, Rank Math or All in One SEO break?
A code review indicated the major SEO plugins are likely to remain compatible, per the Search Engine Journal report. That is an assessment, not a vendor confirmation, so check each plugin's changelog before you upgrade.
Why change the markup at all if it risks breaking plugins?
The change fixes an 11-year-old accessibility bug in which screen readers announced "Select All" instead of the post title. The row header is being moved to the cell holding the object the table is actually about.
Is this specific to Thailand or to any region?
Neither. It is a core WordPress release change and the source makes no regional distinction. Any site upgrading to 7.1 gets the new markup.
Got custom admin columns nobody has looked at since they were built? That is the code to open before 19 August. If you would rather someone else ran the compatibility pass on your WordPress build, get in touch.
