Tag Info

Hot answers tagged

6

You can have multiple sitemaps per website, and this is a great example of when that makes sense. You should make sure you have a Sitemap Index listing each of your sitemaps. It will probably look something like: <?xml version="1.0" encoding="UTF-8"?> <sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <sitemap> ...


5

I'm not sure if this changed over the years since this was asked; while in theory you can (as the first answer states), in practice Google at least will give you an error (as seen in their Webmaster Tools): Incorrect Sitemap index format: Nested Sitemap indexes The Google help page further states: A sitemap index file can't list other sitemap index ...


5

Yes. Everything you ask for is possible. And here's an example XML sitemap file generated by the Drupal XML sitemap module with a little bit of configuration. Everything is done for you out of the box. http://softkube.com/sitemap.xml If you check the code of the XML file there's a link to an XSL and inside that file you can see the code with references to ...


4

Those pages are not high quality pages. Who would want to land on page five of unanswered questions on this site? Nobody. These are low quality pages because: They only a list made of of content found elsewhere on your site. If a user does land on this type of page, they have to click to the content. Even if a user does want a list of this type of ...


4

Yeah. I have seen this too. You are not alone. I don't see any reason to do this. In fact it is redundant isn't it? And since sitemaps are designed to inform search engine about resources to be indexed and sitemaps are not indexed, it seems rather pointless. It was always a silly thing to do. You will see silly things all over the place especially in ...


4

Google looks at things differently than we do. Sorry. That is just the way it is. Sometimes you have to see things from Google's perspective before the data makes sense. The Google Webmaster Tools data lags behind a couple of days and some elements a bit more. As far as the various Index Counts, this explains why the difference. However, there is no direct ...


4

You're better off creating a multilingual sitemap, just to avoid any source of confusion. The format you have shown is correct. In fact, you could even drop the hreflang declarations in your page sections and just use the declaration within the sitemap. The Official Webmaster Tools blog explains the advantages of using the multilingual sitemaps ...


3

Google does not treat CSS content the same as that on page Generally Google will only attempt to index content that is actually embedded within the page content associated with an appropriate tag such as <img>. You can however attempt to force Google's hand by adding the path of the background image into a image sitemap. Some Schema markups require ...


3

There are four valid addresses...and they all show the same site; they are synonyms (no re-direction). Prior to considering your sitemap, which is not essential for Google to index your site, you should deal with all the duplicate content issues you have going on here. As covered in this Google Webmaster Tools help doc: Duplicate content generally ...


3

It seems like you have your HTTP and HTTPS sites redirect to the HTTPS version of your www.example.com. This is good. Just know there is a cost for this initially. In your case, only one sitemap will ever be seen. It is the HTTPS version of your www.example.com site. Any sitemap should reflect both HTTPS and www in the URLs that are listed. Any other URL ...


2

No, you can't submit the exact same sitemap (same syntax, same URLs), and expect Google to sort out what kinds of assets you're trying to identify. If you submit a sitemap that you intend to be for your videos, and it doesn't have the required Video sitemap syntax, and contain the required video-specific tags, Google won't see it as a video sitemap. It's ...


2

Yes, sitemap index files can refer to mRSS files, but you can also submit them individually if you want. You can't link to mRSS files from normal (non-index) sitemap files though. In addition to the help center page you mentioned, there's also a bit about the differences between these files in an older blog post.


2

Install the Yoast SEO plugin on both installations and then add the generated sitemaps to your Google Webmasters account. Google Webmasters allows you to submit multiple sitemaps, so it should be pretty straight forward.


2

Yes that link have nothing to see. But you can use following if you want to remove page from google search : Remove page URL from google


2

Not sure if you saw this. Here is a guide from Google describing tactics for your seperated mobile URL situation: Method for mobile with 2 URL's Basically you set the desktop site as canonical, and mobile as alternate, then use tags to point bots to either-or mode using a preferred hierarchy. Do almost the same for sitemap, only you can use rel and ...


2

Sitemaps have almost no effect on rankings. You don't need a sitemap to have your pages rank well. In fact, it has been suggested that using sitemaps is a red herring. You instead should be spending time making sure your site links to all your content. See The Sitemap Paradox. The only time that I can imagine that submitting fresh sitemaps regularly ...


2

some days ago Give it time! You already have the appropriate 301 redirects set up (by Google) from the old to the new. The old URLs are still indexed. It will take time (weeks, months, ...) for Google to update its index. The only other thing you could do, if you've not already, is to use the "change of address tool". ...


2

The short answer is it doesn't matter. Google doesn't really care where your sitemap is located as long as it can find it. My personal preference would be to have one 'main' sitemap at example.co.uk/sitemap.xml that lists different maps for your site. This way you could have one map for your desktop pages and one for your mobile pages, for example: ...


2

I think that what you'll want to do is change the way your system works. If no language is specified in the URL, but you detect the language via the browser settings, then your site should redirect the user to a URL with that language in the path. This is for two reason: 1) Duplicate content. Spiders/Bots will come to test.com/books, test.com/booken, and ...


2

No, the shortened URL should not go in the XML sitemap. The shortened URL presumably redirects to the long (canonical) URL. Only the canonical URL should appear in the XML sitemap. If the canonical URL is an external resource then that wouldn't be in the XML sitemap either. (The XML sitemap identifies resources on your own site that you want to be ...


2

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 ...


2

Of course. XML is just XML and can be served as XHTML by using XSL if you wish and styled with CSS.


2

Sitemaps have very little effect on SEO. See The Sitemap Paradox. Deleting your old sitemaps shouldn't be an issue. Google will continue to crawl and index the URLs they contain even when the sitemaps are no longer there. In fact, getting Google to forget about URLs is pretty much impossible. If you have new sitemap files that list the URLs you ...


2

Google will automatically crawl links as it finds them unless it runs into a link labeled as "nofollow" or a page with a robots tag containing "nofollow" in it. If you plan to make a webpage on your site as a sitemap page, then try to make it user friendly by giving some sort of description of what each set of target URLs are about. To make google ...


2

Google Sitemap Compression Support It's interesting to read Google's decision to use poorly worded documentation on what sitemaps are or are not supported. Here is a quote from Google Webmaster Tools regarding an error message received when uploading a archived file. Google couldn't process your sitemap because we couldn't uncompress it. This error ...


1

Just delete your website sitemap on Google web master tools, and resubmit your sitemap. Make sure you removed all your unwanted pages, posts and elements from your coding structure. If your are using word press it is better to use Yoast plugin for sitemap because it gives an option to choose which pages, posts and elements to get added on your sitemap and ...


1

Reply to question 1: As the domains are different, in this case, one domain and one subdomain I suppose the sites are different too and therefore you should have one sitemap for your Desktop site and one for the Mobile version of it in the same way that you should add Google Webmaster code and verify both sites independently, thus allowing you to submit ...


1

Don't forget that there is also a 50MB limit to the uncompressed sitemap size. If each of your 50,000 pages had 1,000 images and each image entry in your sitemap were 50 bytes, your entire sitemap would end up being about 2GB. Clearly that is too large. Even including about 20 images per page would put you right about at the 50MB limit. I can't find any ...


1

According to https://developers.google.com/webmasters/mobile-sites/mobile-seo/configurations/separate-urls, we need to add rel=alternate to our sitemap and rel=canonical to the corresponding page on the site.


1

Just the fact that a URL is in the sitemap means that Google is likely to view it as the canonical page. In your sitemap, include only the canonical URL but not the non-canonical versions. Source: The Sitemap Paradox where Google's John Mueller discusses what Sitemaps are good for and says: Recognizing preferred URLs for canonicalization (there are ...



Only top voted, non community-wiki answers of a minimum length are eligible