Hi @wafwaf,
Thanks for reaching out, and I apologize for the inconvenience caused!
Could you please provide more information about the problem?
What data are you referring to, and which tables in the database are affected?
If possible, please share a screenshot/screencast of the problem so that I can investigate this and assist you further.
You can use snipboard or loom to share the screenshots/screencasts.
I’m looking forward to helping you.
Thanks!
Hi @wafwaf,
We haven’t heard back from you in a couple of days. I’m going to go ahead and close this thread for now. But if you’d like us to assist, please feel welcome to continue the conversation.
Thanks!
Thread Starter
wafwaf
(@wafwaf)
Hello, sorry for the late reply. Attached are the screenshots:
Capture 1: https://snipboard.io/GY1Lvg.jpg
Capture 2: https://snipboard.io/kwlhUY.jpg
Why store the meta title and meta description if they are generated on the fly using data that already exists on the database (on unedited metadata)? Is that data storage redundancy or do it to save render time?
Hi @wafwaf
Thank you for getting back to us!
The aioseo_posts database table stores all of our AIOSEO Settings and TruSEO Page Analysis data for each post/page or custom post.
Here’s a screencast reference – https://a.supportally.com/v/MCt7b8.
So, depending on your site environment and the number of pages/posts or custom posts, a table of 56.1MB is to be expected.
I hope this answers your question.
Please let me know if you have any further questions or concerns, and I will be happy to help!
