Jump to content

Lance...

Members
  • Posts

    2
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Lance... reacted to Jordan Miller for a blog entry, New feature! A friendly reminder before posting   
    There’s a fine line between freedom of speech and censorship. 
    Invision Community always aims to empower community leaders with options to encourage an open dialogue within a community, while including barriers for members who choose to ignore the guidelines. 
    Invision Community’s latest release, 4.6.11, includes a simple but powerful new feature to help you shape your community’s tone. 
    It’s called Block Submission.
    Block submission stops a member’s message from being posted if it includes any word(s) added to your Word Filters list with the “Block Submission” option enabled. 
    Word Filters, a previously existing feature, allows community owners to prohibit profanity in the community. If a member types a word included on the banned words list, the platform will automatically either...
    Replace the word with something else you set Hold the post for moderation Or, with our new Block Submission feature, notify the member they must amend their post.  Located: ACP -> System -> Settings -> Posting -> Word Filters -> Add Word Filter
    Here is an example:
    I added the word “hate” to the Word Filters list in the Admin Control Panel and selected the Block Submission option. 
     

     
    Now, when a member tries to post the word hate, a message pops up indicating it wasn’t published and why. 


     
    The member must modify their comment in order for the post to go live. In this scenario, that would look like taking out the word hate.
    Feel free to change the default warning message (the text located in the orange message bar above) to something better suited for your community - it's located in the Languages settings in your ACP. 


     
    Why did we create Block Submission?
    This feature not only helps automatically moderate content, but more importantly, it sets a precedent to members regarding what is (and isn’t) accepted. 
    Gently notifying members that their comment doesn’t align with your community’s guidelines helps maintain the existing culture you’ve worked hard on cultivating, as well as your initiative to keep the language and sentiment positive. 
    Interested in trying our block submission feature out? Please upgrade to 4.6.11!
    If you don’t have an Invision Community license yet, please reach out to me and I’ll help get you started. 
    Thoughts on our latest feature? Sound off in the comments (just make sure it passes our new vibe check 😉). 
     
  2. Like
    Lance... reacted to Matt for a blog entry, SEO: Improving crawling efficiency   
    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.
  3. Like
    Lance... reacted to Ehren for a blog entry, 4.5: ACP Dark Mode   
    A short while ago we revealed the new look Admin CP for Invision Community 4.5. The focus was on increasing the workspace, brightening and modernising the look.
    However, for some this new look was perhaps a little too bright, especially when setting your OS to use dark mode.
    Rather than cause an increase in sales for sunglasses, we went ahead and implemented a dark mode for the Admin CP.
    You can set it to work inline with your OS preference, or you can choose to enforce light or dark mode.
    I'm sure the next question you're about to ask is "Hey Ehren that looks amazing and now working at 3 am won't wake up the neighbours when I log into the AdminCP but can you do the same for the front-end?"
    The short answer to that is "no". The theme system isn't currently designed to support both light and dark colour schemes, however our marketplace has a great selection of dark themes to enhance your community.
    I hope that you like this new feature and I just wanted to say thanks for your feedback; we do listen!
×
×
  • Create New...