Jalal arefen

Gathering information, then understanding what to do with it, is essential for sustainability.
Reporting tools available in the Invision Community platform can help you better understand the inner workings of your community and decide whether your current setup is leading you towards or away from your bottom line.  We recognize that knowledge is power, so we expanded our extensive list of reporting metrics.
Invision Community’s latest release, 4.6.8, includes additional reporting tools in the Admin Control Panel (ACP) to empower community leaders. 
Now, community leaders can not only check registration count, topic creation, device usage and other engagement metrics, but may also view reports on follower statistics, top referrers, member preferences and more. In this post, we'll highlight a couple of our favorite metrics included in 4.6.8.
 
New! Metrics to better understand moderator actions:
# of warnings given: track how many warnings moderators issued during a defined time period. # of suspended users: track how many members moderators suspended during a defined time period. # of reports submitted over a defined period of time.
 
 
Moderator actions include any action a moderator takes in the community, for example hiding/closing/deleting a topic. 
Understanding how your moderators handle sticky situations builds trust and clarity. However, a moderator’s value shouldn’t depend on the amount of warnings / suspensions given. Ideally, a well functioning community with a clear set of guidelines creates a culture where toxic members (and their posts) are less common. Don’t punish a moderator for taking less restrictive action; reward them because they didn’t have to! 
Why you should care: because metrics are imperative for goal setting.
For example, “we want to reduce the number of warnings given by 50% at the end of the year.” In this scenario, the overarching goal is to foster a better user experience, resulting in less problematic posts (and thus less opportunity for moderators to issue warnings). 
If X then Y: If moderators issued 50% less warnings, then their time is freed up to spend on other important tasks.
 
Related: 5 quick tips to up your community moderation game
 
New! Metrics to understand whether your spam defense tactics are working:
 
Unlikely to be a spammer Possibly a spammer Likely to be a spammer  Known spammer
 


No one likes a spammer. Unlike the junk you receive in your physical or email inbox, Invision Community includes powerful tools to combat spam.
Our new spam defense metrics let you know if the systems you put in place are working, or if there's room for improvement. We integrated an intelligent spam defense system directly into the platform, as well as a few additional steps to avoid spam, including an invisible reCAPTCHA and question and answer challenge.
Why you should care: because spam hogs resources and clutters a community.
The higher the "unlikely to be a spammer" stats are in comparison to "possibly a spammer," "likely to be a spammer" and "known spammer," the better. With the new metrics, you'll know without a shadow of a doubt how frequently spammers are flagged and blocked.  
If X then Y: If there are 75% less spammers per month, then your community's health has increased.
 
Related: 3 major improvements we made to spam management
 
But wait... there's more!  Here are additional metrics included in 4.6.8:
 
Members with the most followers Members following the most people Number of content items deleted  RSVPs to calendar events Questions with the most up/down votes over time Member preferences Most-used theme Most-used language
Information is one of the most valuable resources for any community leader because it prompts inspired action. The additional reporting metrics included in 4.6.8 will be made available to you in the first half of November.
Thoughts on our new reporting tools? Drop us a line in the comments. 

No matter how good your content is, how accurate your keywords are or how precise your microdata is, inefficient crawling reduces the number of pages Google will read and store from your site.
Search engines need to look at and store as many pages that exist on the internet as possible. There are currently an estimated 4.5 billion web pages active today. That's a lot of work for Google.
It cannot look and store every page, so it needs to decide what to keep and how long it will spend on your site indexing pages.
Right now, Invision Community is not very good at helping Google understand what is important and how to get there quickly. This blog article runs through the changes we've made to improve crawling efficiency dramatically, starting with Invision Community 4.6.8, our November release.

The short version
This entry will get a little technical. The short version is that we remove a lot of pages from Google's view, including user profiles and filters that create faceted pages and remove a lot of redirect links to reduce the crawl depth and reduce the volume of thin content of little value. Instead, we want Google to focus wholly on topics, posts and other key user-generated content.
Let's now take a deep dive into what crawl budget is, the current problem, the solution and finally look at a before and after analysis. Note, I use the terms "Google" and "search engines" interchangeably. I know that there are many wonderful search engines available but most understand what Google is and does.
Crawl depth and budget
In terms of crawl efficiency, there are two metrics to think about: crawl depth and crawl budget. The crawl budget is the number of links Google (and other search engines) will spider per day. The time spent on your site and the number of links examined depend on multiple factors, including site age, site freshness and more. For example, Google may choose to look at fewer than 100 links per day from your site, whereas Twitter may see hundreds of thousands of links indexed per day.
Crawl depth is essentially how many links Google has to follow to index the page. The fewer links to get to a page, is better. Generally speaking, Google will reduce indexing links more than 5 to 6 clicks deep.
The current problem #1: Crawl depth
A community generates a lot of linked content. Many of these links, such as permalinks to specific posts and redirects to scroll to new posts in a topic, are very useful for logged in members but less so to spiders. These links are easy to spot; just look for "&do=getNewComment" or "&do=getLastComment" in the URL. Indeed, even guests would struggle to use these convenience links given the lack of unread tracking until logged in.  Although they offer no clear advantage to guests and search engines, they are prolific, and following the links results in a redirect which increases the crawl depth for content such as topics.
The current problem #2: Crawl budget and faceted content
A single user profile page can have around 150 redirect links to existing content. User profiles are linked from many pages. A single page of a topic will have around 25 links to user profiles. That's potentially 3,750 links Google has to crawl before deciding if any of it should be stored. Even sites with a healthy crawl budget will see a lot of their budget eaten up by links that add nothing new to the search index. These links are also very deep into the site, adding to the overall average crawl depth, which can signal search engines to reduce your crawl budget.
Filters are a valuable tool to sort lists of data in particular ways. For example, when viewing a list of topics, you can filter by the number of replies or when the topic was created. Unfortunately, these filters are a problem for search engines as they create faceted navigation, which creates duplicate pages.

The solution
There is a straightforward solution to solve all of the problems outlined above.  We can ask that Google avoids indexing certain pages. We can help by using a mix of hints and directives to ensure pages without valuable content are ignored and by reducing the number of links to get to the content. We have used "noindex" in the past, but this still eats up the crawl budget as Google has to crawl the page to learn we do not want it stored in the index.
Fortunately, Google has a hint directive called "nofollow", which you can apply in the <a href> code that wraps a link. This sends a strong hint that this link should not be read at all. However, Google may wish to follow it anyway, which means that we need to use a special file that contains firm instructions for Google on what to follow and index.
This file is called robots.txt. We can use this file to write rules to ensure search engines don't waste their valuable time looking at links that do not have valuable content; that create faceted navigational issues and links that lead to a redirect.
Invision Community will now create a dynamic robots.txt file with rules optimised for your community, or you can create custom rules if you prefer.

The new robots.txt generator in Invision Community
Analysis: Before and after
I took a benchmark crawl using a popular SEO site audit tool of my test community with 50 members and around 20,000 posts, most of which were populated from RSS feeds, so they have actual content, including links, etc. There are approximately 5,000 topics visible to guests.
Once I had implemented the "nofollow" changes, removed a lot of the redirect links for guests and added an optimised robots.txt file, I completed another crawl.
Let's compare the data from the before and after.
First up, the raw numbers show a stark difference.

Before our changes, the audit tool crawled 176,175 links, of which nearly 23% were redirect links. After, just 6,389 links were crawled, with only 0.4% being redirection links. This is a dramatic reduction in both crawl budget and crawl depth. Simply by guiding Google away from thin content like profiles, leaderboards, online lists and redirect links, we can ask it to focus on content such as topics and posts.

Note: You may notice a large drop in "Blocked by Robots.txt" in the 'after' crawl despite using a robots.txt for the first time. The calculation here also includes sharer images and other external links which are blocked by those sites robots.txt files. I added nofollow to the external links for the 'after' crawl so they were not fetched and then blocked externally.

As we can see in this before, the crawl depth has a low peak between 5 and 7 levels deep, with a strong peak at 10+.

After, the peak crawl depth is just 3. This will send a strong signal to Google that your site is optimised and worth crawling more often.
Let's look at a crawl visualisation before we made these changes. It's easy to see how most content was found via table filters, which led to a redirect (the red dots), dramatically increasing crawl depth and reducing crawl efficiency.

Compare that with the after, which shows a much more ordered crawl, with all content discoverable as expected without any red dots indicating redirects.

Conclusion
SEO is a multi-faceted discipline. In the past, we have focused on ensuring we send the correct headers, use the correct microdata such as JSON-LD and optimise meta tags. These are all vital parts of ensuring your site is optimised for crawling. However, as we can see in this blog that without focusing on the crawl budget and crawl efficiency, even the most accurately presented content is wasted if it is not discovered and added into the search index.
These simple changes will offer considerable advantages to how Google and other search engines spider your site.
The features and changes outlined in this blog will be available in our November release, which will be Invision Community 4.6.8.