SEO Audit 1.4.0
- Thread starter qubn
- Start date
Noted! I'll take a look as to why that's happening and push a fix for it as soon as possible.
qubn updated SEO Audit with a new update entry:
SEOAudit v1.3.4 - Duplicate Meta Description Fix
Read the rest of this update entry...
SEOAudit v1.3.4 - Duplicate Meta Description Fix
Read the rest of this update entry...
Give 1.3.4 a try, the issue you reported should be resolved.
Nah, it definitely does look like it
@qubn
Releasing DELETE operations creates row or table-based locks on the tables. The query lasting approximately 1.5 minutes (89 seconds) causes the database to experience heavy disk I/O during that time, indirectly leading to continued queuing of other XenForo tables.
Code:
# Rank Query ID Response time Calls R/Call V/M Item
# ==== ============================ ================= ===== ======= ===== ====
# 18 0x993DF81CC43DDE9FEF5FF0D... 714.6927 0.4% 8 89.3366 0.14 DELETE xf_qubn_seoaudit_autofix_logReleasing DELETE operations creates row or table-based locks on the tables. The query lasting approximately 1.5 minutes (89 seconds) causes the database to experience heavy disk I/O during that time, indirectly leading to continued queuing of other XenForo tables.
Hey, sorry for the delay. I've been quite busy lately and haven't been able to push any updates to the add-on. I'll try my best to get that solved this week. I'll tag you once I got something.
qubn updated SEO Audit with a new update entry:
SEO Audit v1.4.0 - Grant access without super-admin, faster auto-fix-log cleanup
Read the rest of this update entry...
SEO Audit v1.4.0 - Grant access without super-admin, faster auto-fix-log cleanup
Read the rest of this update entry...
That table is the auto-fix debug log. It only fills up when the "Debug logging" option under Auto-fix settings is turned on, and it logs an entry per auto-fix injection, so on a busy board with it left on it can get huge. The cleanup cron was doing a single DELETE for everything past the retention window, which is what gave you that ~90s locking statement and the I/O storm.
v1.4.0 changes the cleanup to delete in bounded 1000-row chunks instead of one big statement, so each delete is short and releases locks between batches, even if the table has grown into the millions. I also added a "Clear log" button on the Auto-fix log page so you can wipe it instantly (it uses TRUNCATE) instead of waiting for the cron to drain it.
If you don't actually need the debug log, leave that option off and the table stays empty. Grab v1.4.0 and let me know how it behaves on your server.
Done in v1.4.0. There's now a dedicated "SEO Audit" admin permission. You can grant it to a moderator or administrator's admin account and they'll get access to SEO Audit without needing super-administrator (and without giving them the whole "Checks and tests" section).
After you upgrade, go to the admin account you want to give access to and tick the new "SEO Audit" permission.
It's the auto-fix log, and you're right that it was hard to find before. In v1.4.0 it shows up in the AdminCP sidebar under Tools > Checks and tests > SEO Audit > Auto-fix log, and there's also a link to it from the SEO Audit dashboard.
One thing to note: that log only records entries while the "Debug logging" option (under Auto-fix settings) is enabled. With it off, the page is there but empty, which is probably why it looked like there was no log.
Ha, yeah, that's the reality of it. People write posts for people, not search engines, and that's fine. The idea with this addon isn't to turn your members into SEO writers, it's to catch the basics that you can actually fix at the platform level (friendly URLs, meta descriptions, schema/JSON-LD, thin/duplicate stuff) so the forum itself isn't holding you back. The score is just a way to see what's worth a few minutes vs what isn't.
Great addon!
It would be helpful if there was an option to exclude specific nodes from the scan (like private nodes, or special-permissions nodes), that aren't exposed to crawlers like Google, and therefore doesn't effect the SEO score.
I saw this option is available with manual scan, but not in the cron (weekly/montly) scans.
It would be helpful if there was an option to exclude specific nodes from the scan (like private nodes, or special-permissions nodes), that aren't exposed to crawlers like Google, and therefore doesn't effect the SEO score.
I saw this option is available with manual scan, but not in the cron (weekly/montly) scans.
I have a problem
When I run an SEO check on my website, it shows that the plugin is grabbing the entire thread text and treating it as the meta description. How can I separate it or do something to prevent it from picking up the whole thing? For example this is one
onlytradersfans.com
When I run an SEO check on my website, it shows that the plugin is grabbing the entire thread text and treating it as the meta description. How can I separate it or do something to prevent it from picking up the whole thing? For example this is one
News Crypto - Reserva de Bitcoin de Trump: disputas entre departamentos complican su creación
La administración Trump ha propuesto la creación de una Reserva Estratégica de Bitcoin, un plan que pretende posicionar a Estados Unidos como líder en el ecosistema de criptomonedas. Sin embargo, este ambicioso proyecto se enfrenta a serios obstáculos debido a la lucha entre dos departamentos...
onlytradersfans.com
