#5173 closed defect (bug) (fixed)
Centralise all the SEO fixes
Reported by: | dd32 | Owned by: | dd32 |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | General | Keywords: | has-patch |
Cc: |
Description
Over the last year we've been closing a lot of random small SEO tickets, but overtime a lot of the changes have had different fixes in different locations, often missing edgecases.
This is an attempt at removing most of the common logic into a single location, with each site filtering the defaults when needed.
Unfortunately, this is more complex than I had expected for some sites (bbPress I'm looking at you).
Change History (21)
This ticket was mentioned in PR #7 on WordPress/wordpress.org by dd32.
4 years ago
#1
This ticket was mentioned in Slack in #bbpress by casiepa. View the logs.
4 years ago
#3
@
4 years ago
Unfortunately, this is more complex than I had expected for some sites (bbPress I'm looking at you).
How can I be helpful?
If bbPress needs changes to help make SEO tweaks easier, let’s make them happen! ❤️
#4
@
4 years ago
If bbPress needs changes to help make SEO tweaks easier, let’s make them happen! ❤️
Unfortunately it's not a simple change. I probably shouldn't have called out bbPress like that, o2 has similar problems, it was just a frustration point that had delayed me making this ticket for a few weeks.
There's two major pain points with bbPress, the first is that forums/topics/replies are not queried until they're displayed, which means that in order to output archive/noindex/etc in the header we have to trigger the queries earlier (See this code but search for // Populate bbpress()
in that file for more. I'm 99% certain we cause everything to be queried twice when that happens too.
The second isn't bbPress's fault, it's the crazy amount of logic that is being requested to noindex things (you'll find more query triggering in there). I'm starting to think we'd be better off noindexing all of bbpress and selectively removing it..
The first would be helped greatly if it were altering the global $wp_query
object rather than making it's own, but that would require a significant change in how bbPress works, and would mean it can't be embedded within other pages as easy, so not really an option, it's just something we have to deal with :)
#5
@
4 years ago
Just a note that this ticket has been sitting while I've continued to test the code, picking up edge-cases and PHP warnings all the existing canonical code in different places have been generating.
This ticket was mentioned in Slack in #meta by tellyworth. View the logs.
4 years ago
#18
@
4 years ago
- Resolution set to fixed
- Status changed from assigned to closed
Marking as fixed as no bugs have cropped up.
Ticket: https://meta.trac.wordpress.org/ticket/5173