Jump to content
This topic contains 301 posts. A summary containing the most significant posts is available

Featured Replies

  • Replies 300
  • Views 26.9k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • We've added the timestamp into the sitemap and we're looking to add a tool to quickly rebuild the sitemap on demand.

  • So many misconceptions. If @daveoh were to share his site, you would see it's very clean, well organized, has high quality content and a glance shows his backlink profile is strong. He also has l

  • Just so you know, we're watching this topic and looking at our own stats to build a better picture. The facts we know: 1) Almost every site I've got access to (via friends, etc) have seen a

Posted Images

 

look top right on the sitemap page?

Thanks, I missed that! I see the timestamp now that's it's rebuilt. ?

  • 2 weeks later...

on site maps ,

would it be worthwhile for the invision 'ping' google etc default to be decreased from 24hrs to say 6 or 4 hrs or even better an user defined variable?

from what I have researched 4 or 6hrs or less could work better?

any views?

 

Edited by sound

  • 2 weeks later...
 

Anyone have updates to report after moving to 4.3? I noticed that the number of links in my sitemap is now significantly smaller. I am not sure why that is, I ran the sitemap rebuild function. It's too early to notice any ranking changes. 

I am wondering how sites that have upgraded to 4.3 are doing in google's rank? Any issues? I've also put off upgrading due to concerns about this, but want to be GDPR compliant and am now considering the upgrade.

Currently my site is recovering from the drop I first reported early in this thread, and obviously I want this trend to continue:

image.thumb.png.fe1092ba1a758129dea48defb9290fca.png

image.thumb.png.2e5014dc51c012fa039dc25ee959caa5.png

My sitemap php offers too few indexing URLs to Google.
I used a paid online tool (03/31/2018) and created a sitemap xml that I installed in a rout directory and sent to Google.
Now the index in Google has begun to recover.

73725593_Screenshotat2018-05-24215826.png.0cf01b05665729ba24cb6c43cfec6c94.png

I also think there is a problem with sitemap php.

You may know this already, but in your Google's Webmaster tools be sure to point to the new site map.

 

You may know this already, but in your Google's Webmaster tools be sure to point to the new site map. 

I did it then. I've also uploaded sitemaps_images xml  that Google has already indexed.

This is me:

image.thumb.png.423fd73515bb844d90fe3f06e8588870.png

 

My sitemap php offers too few indexing URLs to Google.
I used a paid online tool (03/31/2018) and created a sitemap xml that I installed in a rout directory and sent to Google.
Now the index in Google has begun to recover.

73725593_Screenshotat2018-05-24215826.png.0cf01b05665729ba24cb6c43cfec6c94.png

I also think there is a problem with sitemap php.

What tool did you use? I was really hoping that 4.3 would fix the sitemap issue, but all I see is that it significantly reduced the size of the site map and my rankings are getting lower. 

 

You may know this already, but in your Google's Webmaster tools be sure to point to the new site map.

What do you mean the new sitemap? Are you saying it's been moved to something other than sitemap.php ?

I just noticed in google webmaster tools that my gallery images in 4.3.3 have invalid urls using Amazon S3. The sitemap is missing the https:// and only listing the image urls as 

//s3.amazonaws.com/ . If you are using Amazon S3 storage with gallery, check your sitemap.

<image:image>
<image:loc>
//s3.amazonaws.com/.........
</image:loc>

 

Is this really starting all over again? How many times does it have to be pointed out that URL delisting shown in the Search Console cannot be caused by the sitemap generation?

Listing and delisting happens when Google crawls the actual URL and it is decided based on what it finds on that URL. That’s it!
The sitemap can only help Google to find the URL faster. Nothing in the sitemap will cause an URL to be delisted. How could it? It’s just URLs saying “please check this out, Google!”. No slow or incomplete sitemap will cause delisting. No faulty sitemap will cause delisting. No entirely missing sitemap will cause delisting. Nothing in the sitemap can cause delisting. 

If you find an actual bug in the sitemap creation you can demonstrate to be true, better open a support ticket or start a new topic about this bug and nothing else instead of adding it to this huge pile of “I don’t like my Google stats and I will just blame IPS and ask them to fix it”. 

For me on one of my sites it looks like after upgrade to 4.3 there are less urls in the sitemap. However, indexed pages are not affected and seem to be slowly moving up. Right where the submitted dips is when I moved this site to 4.3 but Indexed in red is the same and slowly rising. 

image.thumb.png.65f94da624f28aed6910faab46e7263e.png

My apps using Amazon S3 for storage as I mentioned are causing an issue in google and getting flagged for incomplete <loc> urls and are primarily images and video I noticed. I opened a ticket with IPS, but if anyone else is using Amazon for storage, would be great if you could confirm if your sitemap is listing the complete urls to the file location or not.  Thanks.

Edited by AlexWebsites

Just to add that when i upgraded to 4.3, i used the new option in ACP to rebuild the Sitemap.

 

used the new option in ACP to rebuild the Sitemap.

Where is?

 

Just to add that when i upgraded to 4.3, i used the new option in ACP to rebuild the Sitemap.

Wait what? Where is the rebuild option? Thank you

  • 5 weeks later...
 

I just noticed in google webmaster tools that my gallery images in 4.3.3 have invalid urls using Amazon S3. The sitemap is missing the https:// and only listing the image urls as 

//s3.amazonaws.com/ . If you are using Amazon S3 storage with gallery, check your sitemap.

<image:image>
<image:loc>
//s3.amazonaws.com/.........
</image:loc>

 

This has thankfully been fixed in 4.3.4

 

 

For me on one of my sites it looks like after upgrade to 4.3 there are less urls in the sitemap. However, indexed pages are not affected and seem to be slowly moving up. Right where the submitted dips is when I moved this site to 4.3 but Indexed in red is the same and slowly rising. 

image.thumb.png.65f94da624f28aed6910faab46e7263e.png

My apps using Amazon S3 for storage as I mentioned are causing an issue in google and getting flagged for incomplete <loc> urls and are primarily images and video I noticed. I opened a ticket with IPS, but if anyone else is using Amazon for storage, would be great if you could confirm if your sitemap is listing the complete urls to the file location or not.  Thanks.

With the sitemap in 4.3.3 and 4.3.4 now fixed, my indexing has gone up from 17849 pages to 22,229 (pretty much over the last 4 weeks) with just about the same submitted, less the new content. I do believe adding the timestamp helped and I'm still waiting for all my images to be indexed because before the latest ips sitemap change, google was not picking up the extra image sitemap or video sitemap. Now there is clearly a content section for images and video as separate sitemaps within the sitemap.  I do think there is an opportunity for those that want to use it, to include additional topic and other secondary content pages in the sitemap as well as a news sitemap for those that use the pages app.

 

image.thumb.png.a931f3449e451b36380ae0ea01f07b43.png

  • 4 months later...
 

image.thumb.png.a931f3449e451b36380ae0ea01f07b43.png

Just a quick comparison, this snapshot was taken in June and today I'm gong further down on the same site in terms of indexed pages from the built in IPS sitemap. Looks like almost 8k in pages no longer indexed. In addition to that, this site is down about 30% in traffic now in October.

image.thumb.png.41f53e3daa730316fdb20816520c721f.png

  • 1 month later...

We have 1407 sitemaps. The oldest is more than 1 month old and the newest one is 4 days old. And we have decrease in Google indexed page. Is there still an issue with large sitemaps?

  • 3 weeks later...

@Sonya* yes, and it will stay issue as long as IPS does not change the sitemap mechanism and structure.

 

@Sonya* yes, and it will stay issue as long as IPS does not change the sitemap mechanism and structure.

@SeNioR- What are you suggesting IPS change with the mechanism and structure?

  • 1 month later...
 

Just a quick comparison, this snapshot was taken in June and today I'm gong further down on the same site in terms of indexed pages from the built in IPS sitemap. Looks like almost 8k in pages no longer indexed. In addition to that, this site is down about 30% in traffic now in October.

image.thumb.png.41f53e3daa730316fdb20816520c721f.png

Just thought I'd share. It's getting worse....here's my current sitemap index results. This site has over 12k topics, so they are not all getting indexed for some reason. 

image.thumb.png.5a76429b943d624bafc9abf6aa2fa19c.png

 

Just thought I'd share. It's getting worse....here's my current sitemap index results. This site has over 12k topics, so they are not all getting indexed for some reason. 

Well, this graph doesn’t show the reasons. Have you switched to the view that does? I mean this one:

1960992634_Bildschirmfoto2019-02-08um16_23_18.thumb.png.b9bf0f18504572620c3dac65efed90c5.png

Recently Browsing 0

  • No registered users viewing this page.