New answers tagged sitemap
It seems these days that a sitemap in the root named sitemap.xml will get picked up by dang near anyone in time. It all depends on how much control you want. If you do not want just anyone reading your sitemap including scrapper bots, then name it something unique and submit it to Google, Bing, and who ever else you want. Do not put it in your robots.txt ...
Yes, definitely include them in your main sitemap. You still want your product URLs indexed as fast as possible, and a sitemap will help with that.
I have a few forums. But there is one common problem with them. There are at least 2-3 spam threads per day on each forum. So If you submit all the new urls to sitemap, spam threads will be indexed too. Which one engine do you use for your forum? I use phpBB for my forums. And there is "phpBB3 SEO Sitemap" plugin doing this work. So you should to find ...
It's very simple. php maintenance/generateSitemap.php \ --fspath sitemap \ --server http://example.org \ --urlpath http://example.org/sitemap See the generateSitemap.php manual for more information. The DIY solutions suggested by the other answers are suboptimal.
A sitemap is not for pages that are constantly changing. It's for showing the structure of a site, not new content of each page. If you are constantly adding and changing that many pages a day, which sounds strange to me, that is what a RSS or Atom feed can be used for. Google, at least, looks for those to indicate changes within pages that are already ...
I have Wordpress with forum. Wordpress sitemap plugin re-create sitemap.xml every time when a new page is created. It happens automatically.
Yes, it's correct to target the countries in the sitemap.xml and point them to the regional url. And yes, you can use the same URL for multiple locations. You might want to simplify it here though, and use /us/ for "en" (all English variations that aren't otherwise specified) and /uk/ for "en-gb" (just English in Great Britain). If possible, use the ...
FWIW... on the face of it Google would seem to be incorrect in my opinion. Or rather, it's implementation of the standard (RFC 3986) is too strict. (Although systems do vary in this respect.) URLs always need to be suitably URL encoded / percent-encoded (as @mike states) by encoding characters that have special meaning, and then XML entity encoded when used ...
Top 50 recent answers are included