sadams101

After further examination, many of the profiles currently in my list of crawled but not in index SHOULD be in the index--but I don't believe that profiles are in the sitemap. If this is correct, my next project is a sitemap for profiles, and I am also looking into this for article comments as well. The more detailed the sitemap the better.

Indeed that is currently what is not in the index due to the "noindex" tags now in profiles without data, but 80% of the pages in this list were regular forum topic and post pages, and those appear to be going back into the index now. It was a 61% drop in the crawled but not indexed. So what you used to see here were lots and lots of links that SHOULD HAVE BEEN in the index...many of those are now gone.

I want to report a HUGE drop in my site's pages that are no longer in Google's index. As mentioned, I implemented the new custom posts sitemap on April 4th, and that is the day I also added the new sitemap to Google Search Console. As you can see below, since January I was seeing VERY SLOW drops in the number of pages not in google's index, and then on April 8th I saw a dramatic drop from 488,367 crawled but not indexed, to only 186,713. This is clearly a dramatic drop in non-indexed pages. I realize that this isn't necessarily proof of concept here, but certainly my new sitemap has not hurt me as some of you predicted, and in my opinion it is solving this issue. I've read lots of Googles posts on this topic, and the bottom line is that if it isn't in your sitemap you are telling Google's spider that it isn't important.

After closer inspection I believe I found the issue, which was caused by an errant div tag for code I changed. If anyone is interested I have SuperTopics and SuperGrid working with defer image load.

I am having an issue with SuperTopics where I have created a latest posts feed block that is in my bottom-right area in the right column. If I put any other block below it, the additional blocks are broken and pushed into the center main area--so they are not in the right column. I have 3 items in my SuperTopics post bloc, and have noticed that the last item at the bottom doesn't accept the font formatting that the top 2 items use. Because I was not able to edit any blocks that I added below my SuperTopics post feed in the right column, I created a support ticket with IPB, and they said that there is an issue with SuperTopics that is causing this. I am reporting this as a possible bug.

The extra pages sitemap is now finished...anyone interested can contact @DawPi https://www.celiac.com/sitemap_pages.php

Ok, but this never happened until I ran SuperGrid, and the grid gets broken somehow. It seems to be intermittent, as sometimes the cache seems fine, but other times it breaks. Also, and I saw your comment to another poster here with this issue, but on the article/page view there seems to be a lot of white space to the left of the article. I do have my database page set to one column, which was the recommendation to fix this issue. Is there any way I can make this article widen out to the full page?

I am using the latest version of SuperGrid, and am having an issue where if I use the "Cache page output for guests" all of the pages that use the SuperGrid template are malformed. If I turn off this cache they look fine. The problem is that I need to use the cache. I would appreciate any help to fix this. See below with cache on: With cache off:

I appreciate your input here, and concerns with the new posts sitemap. As you know it will take time to see whether or not this will be a good or bad thing. I do understand the canonical link situation, but one positive I can think of for this would be that it will still direct google search to include all topic pages that have more than one page. For example, this is not in the sitemap: https://invisioncommunity.com/forums/topic/442742-large-community-you-have-a-problems-with-sitemap/page/10/ nor are pages 9, 8, 7. 6, etc. Only page 1 is in the sitemap. To Google, at least how I've learned to interpret their sly "Google Speak," the message you are sending to Google by not including these pages in your sitemap is that the content on those pages it not important enough to include in their index. After all, they do say that if you want it included in their index, submit the page to their index. They have 2 ways to do this--1) manually; 2) use a sitemap. On a side note, we're also developing a separate sitemap just for those extra topic pages. Overkill? Maybe. We'll see...

@DawPi has completed the custom sitemap application that I mentioned which handles all posts. You can see an example of it here: https://www.celiac.com/sitemap_posts.php but it is modeled after the existing sitemap--but this one handles just forum posts. We were not able to add a minimum word count to this application, as one person suggested, because it slowed things down and put a load on the CPU. We were, however, able to add the ability to exclude certain forums, for example my site has around 25 different forums, so I was able to exclude a general chit chat and a technical support forum that are more or less off the main topic of my site. Whether or not this will be a benefit or liability in Google search is an open question, but I'll follow up here with any noticeable changes, positive or negative. I believe this will have positive results, simply because we are making it easier for Google to index specific content and allow them to provide more relevant search results for any given query. Currently Google's results may send people to a topic page like this one /page/10/, and the person who searched will still have to fish on it for the specific results of their query. With all posts indexed, Google should be able to send the person directly to the content that answers their query...at least that is my hope here. Anyone interested in this app can contact @DawPi Here is a screenshot of the admin page:

So I'd like to follow up about the terrible downward spiral of my site that began around August 2018--it dropped from a USA site rank of ~15K to 85K. Certainly part of it was caused by Google's Medic update, however, a good deal of it, I believe, was also caused by flaws with the IPB sitemap that came back into play on my site (I should have been watching this more closely), and the flaws with how the topics are indexed, both of which were corrected in 4.4. Around April 2018 I used this thread to fix the lastmod issue in the sitemap in version 4.3, which had a very positive impact in Google search--my site rose from a ~30k rank to ~15K in the USA. The problem was that the modifications I did were done in a way in which they could get overwritten, and at some point after August 2018 they were overwritten, and I did not notice this. My site rank kept dropping for months. I updated to 4.4 on March 10th, and since that moment my site is gradually climbing back. This leads me to believe that IPB should really port those fixes now to 4.3 (maybe even 4.2), because they really are flaws in the software that are dragging down the search rank of any site using those versions. The main reason I am posting this, however, is to get an opinion of a possible new plugin that would create a per post sitemap, totally separate from the original sitemap.php, so it would be something like sitemap2.php, that would map every forum post. So, for example all forum links like to individual posts would be in that sitemap: https://www.celiac.com/forums/topic/109854-searching-for-refractory-friends/?do=findComment&comment=933769 The sitemap functionality would work exactly the same as it does now, but it would just focus on the forum posts. I would like to hear pro an con opinions of this approach. To me, I don't see any reason why it would not have a positive impact in google search. Please let me know your thoughts.

I too am running lazy load, but in 4.3 (it's a custom solution that works really well, and is easy to install), and have also noticed that superblocks and supergrid don't work with it. It looks like these plugins load the images in the background. I wish they worked with lazy load.

On mobile I've noticed some formatting issues on the main category page: https://www.celiac.com/articles.html/?show=categories I realize that not everyone is going to have these issues, as my site is quite large, old, and probably has way too many categories and sub-categories (I will be trying to tackle this issue soon). However, the design of this template should probably still take this into account.

I finally figured this out...just in case anyone else needs this: h2 .ipsType_break { font-size:1.5rem; line-height:1.3; } And this is the text area just below: .ipsType_center .ipsType_light { font-size:0.9rem; line-height:1.3; }

For the Supergrid I am hoping that someone might be able to help me to find the CSS to edit the article title/link areas--see the red arrow? This page can also be seen here.

I found it...my bad, please ignore my request. I hope to have better questions about it soon!

Hello, I just purchased this plugin and, unfortunately, don't see a user guide or other instructions for how to use it. Sorry, but going through this thread didn't give me the basic answers I seek. Please let me know, thank you!

I will try this

This fix helped solve the issue: In template Core > global > global > includeJS add "defer" to this line: <script defer src='{{if $js->data['host'] == parse_url( \IPS\Settings::i()->base_url, PHP_URL_HOST )}}{expression="$js->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}{{else}}{expression="$js"}{{endif}}' data-ips></script>

I'm having a problem with PHP & TXT Widget that started a few months ago. It is now triggering render blocking Javascript errors, which it never used to do. Clearly something changed, either with IPB updates, or something else. I am hoping for a fix for this.

Some users report Error 2S129/2 when they try to validate their email. It looks like they click on the link in their email, get this error, then when I check them the account looks fine and activated. Any idea whey they would see this error?

Anyone else who wants to do this try: {{$buttonMethods = $login->buttonMethods();}} {{$usernamePasswordMethods = $login->usernamePasswordMethods();}} {{if $orientation == 'vertical'}} <div class='ipsWidget_inner ipsPos_center ipsPad'> <div class="ipsAreaBackground_light ipsPad"> <h2 class="ipsType_sectionHead ipsSpacer_bottom ipsSpacer_half">{$title}</h2> <p class="ipsType_richText ipsType_contained"> {$text|raw} </p> {{if $usernamePasswordMethods}} <ul class="ipsList_inline"> <li> <a href='{url="app=core&module=system&controller=login" seoTemplate="login"}' class="ipsButton ipsButton_primary ipsButton_verySmall ipsPos_right">{lang="sign_in_short"}</a> </li> <li>{lang="or"}</li> <li> <a href='{url="app=core&module=system&controller=register" seoTemplate="register"}' class="ipsButton ipsButton_primary ipsButton_verySmall ipsPos_right">{lang="sign_up"}</a> </li> </ul> {{endif}} {{if $buttonMethods}} <div class=''> <form accept-charset='utf-8' method='post' action='{$login->url}' data-controller="core.global.core.login"> <input type="hidden" name="csrfKey" value="{expression="\IPS\Session::i()->csrfKey"}"> <input type="hidden" name="ref" value="{expression="base64_encode( \IPS\Request::i()->url() )"}"> {{foreach $buttonMethods as $method}} {{if $method->getTitle() == 'login_handler_Facebook'}} <div class='ipsType_center ipsPos_center ipsSpacer_top'> {$method->button()|raw} </div> {{endif}} {{endforeach}} </form> </div> {{endif}} </div> </div> {{else}} <div class='ipsWidget_inner ipsPos_center ipsPad_half'> <div class="ipsAreaBackground_light ipsPad"> <div class="ipsGrid ipsGrid_collapsePhone"> <div class='ipsGrid_span{{if $buttonMethods}}9{{endif}}'> <h2 class="ipsType_sectionHead ipsSpacer_bottom ipsSpacer_half">{lang="widget_guestsignup_title"}</h2> <!-- lines below removed by scott <p class="ipsType_richText ipsType_contained"> {lang="widget_guestsignup_text"} </p> END removed --> {{if $usernamePasswordMethods}} <ul class="ipsList_inline"> <li> <a href='{url="app=core&module=system&controller=login" seoTemplate="login"}' class="ipsButton ipsButton_primary ipsButton_verySmall ipsPos_right">{lang="sign_in_short"}</a> </li> <li>{lang="or"}</li> <li> <a href='{url="app=core&module=system&controller=register" seoTemplate="register"}' class="ipsButton ipsButton_primary ipsButton_verySmall ipsPos_right">{lang="sign_up"}</a> </li> </ul> {{endif}} </div> {{if $buttonMethods}} <div class='ipsGrid_span3 cSignInTeaser_right'> <form accept-charset='utf-8' method='post' action='{$login->url}' data-controller="core.global.core.login"> <input type="hidden" name="csrfKey" value="{expression="\IPS\Session::i()->csrfKey"}"> <input type="hidden" name="ref" value="{expression="base64_encode( \IPS\Request::i()->url() )"}"> {{foreach $buttonMethods as $method}} {{if $method->getTitle() == 'login_handler_Facebook'}} <div class='ipsPad_half ipsType_center ipsPos_center'> {$method->button()|raw} </div> {{endif}} {{endforeach}} </form> </div> {{endif}} </div> </div> </div> {{endif}}

So I guess I'm stuck on this. I'm not sure what to include for the button name in this line: $method->button()->facebook

Thank you for this. I've been testing but still can't get the facebook button showing. Here is what the facebook code looks like for that button: <div class='ipsPad_half ipsType_center ipsPos_center'> <button type="submit" name="_processLogin" value="5" class='ipsButton ipsButton_verySmall ipsButton_fullWidth ipsSocial ipsSocial_facebook' style="background-color: #3a579a"> <span class='ipsSocial_icon'> <i class='fa fa-facebook-official'></i> </span> <span class='ipsSocial_text'>Sign in with Facebook</span> </button> </div>

Not being a coder I don't see a way to make only the Facebook button appear.