4 Responses

  1. harknell
    harknell January 2, 2008 at 5:07 am |

    One issue you *may* run into with adding .html onto the end of your permalinks with WordPress is some plugins may not work correctly. Specifically image galleries and other things that create their own internal multi-pages that are separate from WordPress’s pages (such as a gallery split across internal pagination). I’m not sure it won’t work correctly, but I’ve seen reports on the support site for WordPress about problems that occurred due to the .html getting in the way of things. (I guess I should eventually check that with my own Image Gallery plugin AWSOM Pixgallery)

  2. Christopher Price
    Christopher Price January 2, 2008 at 8:18 am |

    If they don’t, it’s a plugin bug. If they’re tapping the internal array properly in WordPress 2.X, those bugs shouldn’t surface after version 2.2.2… array bugs regarding .html should have been fixed in 2.3.

    Probably the easiest workaround if you run into those issues is to form such pages as, well, pages… page structure is not affected by standard permalink changes (though if you go under-the-hood, you can change them)… only posts are affected.

    I wouldn’t say it’s not a concern, but it’s a minor one and could probably be fixed easily in most offending plugins.

  3. Techblissonline Dot Com
    Techblissonline Dot Com January 9, 2008 at 3:46 am |

    I am not sure on what you mean by search engines seeing .html and .html#comments as different urls…Do you find both getting indexed in webmaster tools…i don’t think search engines will treat them as different… # is meant to name a location on a webpage…Search engines would not consider them as different…

  4. Christopher Price
    Christopher Price January 9, 2008 at 7:14 am |

    I’ve seen it on search engines other than Google in the past. Google remedied this with BigDaddy technology, like I said above. Of course, the best SEO position is one that doesn’t just take the big three (Yahoo, Live, and Google) into account… but it’s a minor concern.

    The only problem would be if a bunch of big sites (Slashdot, digg, etc) picked up on the #comments link, and other sites (say, national media) started hitting the non-linked version. That could cause a PageRank split on engines other than Google.


Leave a Reply