Implement SEO on archive pages

Hi Paul, there is an extension planned that would enable metabox for Archives and other archive types without UI. It is currently next in line and @cybr (plugin author) says the earliest version that might contain this feature is 3.1.

However, I honestly don’t think it is reasonable to throw specific dates around, because of 2 major setbacks:

1. Technical aspect, how to makes this work without JavaScript among others.
2. Niche request. This request caters needs of very few and TSF currently needs to focus on needs/requests of the many. There are other more requested features that might get priority.

Every feature adds to code base, needs maintenance and brings compatibility concerns (Old PHP, WordPress core, other plugins…). As TSF is still being made by 1 person (@cybr) everything new has to be considered very carefully, because the time is becoming more scarce.

Rushing features might bring up some bad spaghetti in the code, less testing and potentially catastrophic scenarios if there was some major bug to occur. As a linux person, I much more prefer current slower development cycle with time for testing and rock solid stability. Not that there are no new features — Focus was released recently and it is massive addition. It provides users with unique perspective on keywords (you can read more on blog) and this is something that caters to many, it is unique, adds tremendous value in terms of SEO and focuses on the most important aspect of SEO, content. That is, my opinion and you might disagree.

Yes, having a nice description for your archive brings tiny–tinsy SEO benefit, but honestly it is sooo negligible when you consider how much time is needed to implement it as a feature. At least from my own experience, most archive pages are not that great and I think Google knows that too. If you really think otherwise, they can utilize categories or tags for this need (both have SEO metaboxes and make more sense). Or hack away couple of filters.

So if you really need this feature now and other plugins have it, you should use them instead and don’t wait for TSF to implement it. It would be only logical. It is not that we are going to be happy to see you use different plugins, but it is what it is ?? I hope you understand, and I am sorry I can’t produce specific ETA for you.

Thank you for your appreciated and well-thought answer. We agree on many things, but I find it illogical that a WordPress tool like TSF don’t support the templates the tool is designed for. Archive page are a WP feature, so is TSF. So why not support it? Don’t misunderstand me here; I’m thinking binary and I don’t take into account that archive pages possible are rarely used (?) and that it’s a feature that will take very long to develop.

I always use archive-myCustomCPT.php when I want to list all posts in a CPT on a page. How would you do this?

I should mention that this is the prefered method for many, many developers. Thus, I’m not the only one wishing this feature in TSF.

One of many articles describing how to use archive pages:
https://www.wpbeginner.com/wp-tutorials/how-to-create-a-custom-post-types-archive-page-in-wordpress/

Hi @pauloldman,

The plugin’s still relatively new, and I had to include many other features first to get to this point. Archive pages are a fickle thing I never had time to dive in to, and I’ve seen many (bad) iterations among them; so, I held back whilst increasing support for “regular” CPT pages and many other features.
I did this in the last few updates, which were focussed on growth.

Now, support for these pages will be included after v3.1.
Alas, I don’t see how I can easily integrate it yet. This is why I’m going to place it in an extension first; it gives me more freedom without affecting the core framework.

With that said, users are always free to send us PRs, suggestions, and feedback.

Cheers ??