-
Posts
70,143 -
Joined
-
Last visited
-
Days Won
649
Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Projects
Release Notes v5
Invision Community 5 Bug Tracker
Forums
Events
Store
Gallery
Everything posted by Matt
-
I think if you have tags disabled, it's fine to disallow those. Notifications, checkout, subs purchase are all fine to omit. I'm unclear what google will index with 'index.php?*' but this is likely fine as long as you have rewritten friendly URLs on. I'd need to audit to see what 'app=*' would disallow. Generally it should be fine but there may be some functionality that doesn't have a friendly URL. do=download/do=email both fine to disallow. I'll tweak the robots.txt file to include some of those.
-
Hump Day: Facebook name-change may be on the horizon
Matt replied to Jordan Miller's topic in Invision Community Insider
Same as my 13 year old. He thinks of Facebook as some ancient relic washed up on the shore. He is either in Playstation Chat, TikTok or WhatsApp. -
Hump Day: Facebook name-change may be on the horizon
Matt replied to Jordan Miller's topic in Invision Community Insider
I agree. My eldest son is 13 and he doesn't want anything to do with it. It probably has less than a decade left in its current form. -
Hump Day: Facebook name-change may be on the horizon
Matt replied to Jordan Miller's topic in Invision Community Insider
I hope Facebook do something interesting or at least stimulate a new market. I don't think Facebook IS evil, I just think the platform is not fit for the number of active users they have. -
Hump Day: Facebook name-change may be on the horizon
Matt replied to Jordan Miller's topic in Invision Community Insider
This is similar to when Google created Alphabet to enable them to expand into other markets. Clearly Facebook understand that it is past its peak and can now only decline so it makes sense for them to look at where they can go next. I'm not overly keen on living in a Facebook universe though. -
As Stuart mentions, a permalink has to be dynamic to account for issues arising when deleting posts (the page may change) or merging topics, etc. However, it's of little use to guests so they have been removed in November's release.
-
Google - Invalid object type for field "itemReviewed"
Matt replied to desti's topic in Technical Problems
This should be fixed in our November release. -
New notification when content is approved in 4.6
Matt replied to AlexWebsites's topic in Technical Problems
Hi! Apologies for the delay. This is a very high level issue which is greater than just this one notification. Essentially, once you have set your notifications up, any new notification types are not being picked up by your settings without resetting them in the Admin CP. We are working on a solution but it's not a simple fix and we are still working on the best route to take. -
Have you given your browsers permission to use push notifications? There is a little message at the footer of your notification settings page.
-
Without seeing the surrounding code, it's hard to diagnose. It's worth nothing that when you close a dialog, it just gets hidden. You will need to call dialog.remove() if you want to remove it from the DOM. This may be the issue you are seeing.
-
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.
-
This effectively stops them from posting at all.
-
The bug here is no. 4 should use the page title. When you choose to not use categories, then it will use the page details in both H1 and page title I do agree that it's a bit scrappy and we will clarify this in the UI at a later date.
-
What is a robots.txt file? When Google or other search engines come to your site to read and store the content in its search index, it will look for a special file called robots.txt. This file is a set of instructions to tell search engines where they can look to crawl content and where they are not allowed to crawl content. We can use these rules to ensure that search engines don't waste their time looking at links that do not have valuable content and avoid links that produce faceted content. Why is this important? 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 single page, so it needs to decide what to keep and how long it will spend on your site indexing pages. This is called a crawl budget. How many pages a day Google will index depends on many factors, including how fresh the site is, how much content you have and how popular your site is. Some websites will have Google index as few as 30 links a day. We want every link to count and not waste Google's time. What does the suggested Robots.txt file do? The Invision Community optimised rules exclude site areas with no unique content but instead redirect links to existing topics, such as the leaderboard, the default activity stream. Also excluded are areas such as the privacy policy, cookie policy, log in and register pages and so on. Submit buttons and filters are also excluded to prevent faceted pages. Finally, user profiles are excluded as these offer little valuable content for Google but contain around 150 redirect links. Given that Google has mere seconds on your site, these links that exist elsewhere eat up your crawl budget quickly. What is the suggested Robots.txt file? Here is the content of the suggested Robots.txt file. Depending on your configuration, Invision Community can automatically serve this. If your community is inside a directory, you will need to apply it to the root of your site manually. So, for example, if your community was at /home/site/public_html/community/ - you would need to create this robots.txt file and add it to /home/site/public_html. The Admin CP will guide you through this. # Rules for Invision Community (https://invisioncommunity.com) User-Agent: * # Block pages with no unique content Disallow: /startTopic/ Disallow: /discover/unread/ Disallow: /markallread/ Disallow: /staff/ Disallow: /cookie/ Disallow: /online/ Disallow: /discover/ Disallow: /leaderboard/ Disallow: /search/ Disallow: /tags/ Disallow: /*?advancedSearchForm= Disallow: /register/ Disallow: /lostpassword/ Disallow: /login/ # Block faceted pages and 301 redirect pages Disallow: /*?sortby= Disallow: /*?filter= Disallow: /*?tab= Disallow: /*?do= Disallow: /*ref= Disallow: /*?forumId* Disallow: /*?&controller=embed # Sitemap URL Sitemap: https://www.yourURLHere.com/sitemap.php *Note, if you are copying this file, you may need to add the path name and correct the sitemap URL.
-
I've not used the service but I'd imagine it's as straight forward as Zapier. They have some great documentation: https://www.integromat.com/en/help/docs#general
-
Hump Day: 4.6.7 is officially out!
Matt replied to Jordan Miller's topic in Invision Community Insider
The Invision Community release train. Choo-choo! -
Hump Day: 4.6.7 is officially out!
Matt replied to Jordan Miller's topic in Invision Community Insider
Yes, we are aiming for a release every single month which will bring a mix of new features and bug fixes. -
Hump Day: A Refresh Has Arrived!
Matt replied to Jordan Miller's topic in Invision Community Insider
Thanks for being a customer for all those years, and I hope you've enjoyed the journey we've been on. Good luck with your community and let me know if you need any help. 🙂 -
Sorting by highest rating is only based on the 5 star rating value. The sort feature pre-dates the QA vote mode, so it's not take into consideration but I agree that it would be a good change to make it so.
-
I'll make a note to clear up this confusion in the user interface. The title and content fields are special because they fit into the Node\Model framework which underpins this feature.
-
Hi 🙂 We feel that back-ups are best left to dedicated tools that can do them reliably at scale. We want to focus on providing the best set of tools to build a community and leave server management to others. 💪
-
Discord has its place. It's a great tool if you're just starting a community and want to see if there's a need, or you want a semi-asynchronous chat that focuses on a 24-48 hour time window. However, we have a mature support community so it's less useful. We want to encourage thoughtful posts that have a life beyond a few days. We want others to find these topics from search engines and we want to build a crowdsourced knowledgeable for Invision Community. If we were to create an official Discord, it would create a brain drain and instead of us being able to look back and look at feature request trends, or customers being able to search for answers to their questions we have a 'here and now' relatively informal chat room.
-
Hump Day: A Refresh Has Arrived!
Matt replied to Jordan Miller's topic in Invision Community Insider
You have an amazing community, and thank you for sticking with us. 🙂 -
Hump Day: A Refresh Has Arrived!
Matt replied to Jordan Miller's topic in Invision Community Insider
Thank you, I appreciate that. I'm really pleased to hear that you're staying with us. 🙂