Date Archives Redirecting to Homepage, not Corresponding URL
-
Hello,
In reviewing logs of visits to our new site, there are dozens of instances of what appear to be date archives appearing in said logs with a 200 server response, meaning they are visible and indexible. For example: /2019/06/01.
In Yoast > Search Appearance > Archives > Date Archive Settings, “Date Archives” is set to Disabled. We configured this setting before adding content to our site to avoid the creating of date archives. In our sitemap that’s generated by Yoast, there are no instances of date archives. Regardless, they are being crawled and indexed by search engine crawlers as evidenced by the aforementioned visitor logs.
Furthermore, all of these date archives are being redirected to the home page by Yoast via 301 redirects (many dozens of them), according to a redirect checker. From what I understand, redirecting posts/pages to content that has no relevance to the redirected post/page – especially to the home page – is not good at all for SEO.
What can I do to delete all date archives? I don’t want them indexed. If that’s not possible, what can be done to hide them from search engines so they are not indexed?
If neither option is not possible, what can be done so that Yoast redirects all date archives to the relevant page? For example, the post “/cats/cat-treats” was published on “/2019/06/01”, resulting in the date archive slug “/2019/06/01”. If someone inputs the URL”mydomain.com/2019/06/01″, why is it not redirected to “mydomain.com/cat-treats”, which is where the actual content is?
It does not make sense semantically, or with regards to SEO to redirect this date archive to the home page when “cat-treats” has no connection to the home page.
Thanks and have a good day.
- The topic ‘Date Archives Redirecting to Homepage, not Corresponding URL’ is closed to new replies.