• On blogs with a long history, wp_get_archives in your header can lead to a lot of output, populating your header with one of these after the other?
    <link rel=’archives’ title=’January 2009′ href=” />

    I understand what it is. The question is, is anyone actually making use of it, or should it be dropped? Browsers don’t seem to notice it and I can’t find evidence that the search engines care about it either.

Viewing 2 replies - 1 through 2 (of 2 total)
  • I usually take it out. I don’t think that it’s that useful and pushes important content down.

    PLEASE NOTE: cross-posted to WordPress Ideas as well in response to similar discussion.
    ——————
    FWIW, I just had an issue with my host about this. They 403/disabled my site briefly today because of heavy traffic, and told me they had been having issues with traffic load. That was surprising to me (I’m not that popular, grin). Here’s what we finally figured out:

    From my hosting co. customer support:

    Note that we have noted your site causing server load issues on many occasions as a result of your WordPress installation which has a history of not scaling well when heavy traffic hits it.

    “One theory is the Achive links that WordPress adds to your header, if you view the source of your index file you will see a large number of lines of code starting with:
    link rel=’archives’

    “When we see loading issues with your site many times there are a large number of hits for proxy server IPs and the theory is that these proxies are cacheing your site and hitting all of those archive links. Many of the IPs we see when your site is causing loading issues are corporate, educational and Gov’t/Military proxy IPs which appear to prefetch content when someone accesses a site.

    We would recommend removing those archive links and investigating modifying WordPress to not add those back (or additional as time goes on).

    I checked the source and they were right — 7 years of monthly archive links being fetched….

    I removed wp_get_archives from the header and it all seems fine now. But thought it might be of interest to others in this community.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Is wp_get_archives in your header just a waste of space?’ is closed to new replies.