Insytful monthly roundup: April 2025

April brought us bug fixes, infrastructure improvements, quality of life changes, and roadmap planning for the summer.

We also welcomed Actegy onboard. Their web content spans 11 countries, and they use Insytful to comply with the EAA. They were up and running immediately, using the Jira integration, sections, and multilingual dictionary features.

We migrated our scanning and processing infrastructure to a new, updated Kubernetes cluster. This update allows us to better monitor downtime and scale more easily during peak scan periods. Although there should be no real difference within the app:

• Site scans will now be able to handle more concurrent scans and requests.
• Individual scans will get picked up faster.
• The update will reduce potential outages.

Modern sites are good at detecting if a request comes from an automated scanning tool and will block it. Unfortunately, they often block requests using an inaccurate status code, such as 404.

This makes it difficult to know if a link is actually broken, or if we are being blocked.

To rectify this, we have changed how we make requests when checking for broken links on external domains. With the new change, you will find fewer false positives in content quality. We have some further iterations planned for this, which are scheduled over the next few months.

We have been working on integrating with Google's Web Risk API. This integration allows users to ensure their site doesn't contain links to malicious, phishing, or malware pages.

Site administrators can supply their API keys to turn this feature on, which will look for malicious links during the scan process. This feature will be rolled out in the next couple of days, as it is going through the final round of testing.

• Related Jira issues can now be easily removed from Insytful.
• The individual page view mobile breakpoint has been increased. In addition, audits received some love to work better on smaller screens, which is especially useful for those on smaller laptop screens.
• Spacing on the title bar now works on smaller screens, and URLs and page titles now collapse and truncate to keep items visible.
• A bug fixed where users who weren't logged in couldn't preview their entries from Contensis within Insytful.
• A bug fixed which wasn't doing the right error code in the app when something went wrong.
• A bug fixed where the Jira integration button was not showing in certain scenarios.

We have some exciting features and work streams coming up over the summer, not necessarily in this order.

Nothing is worse than putting together a cornerstone content webpage with well-written copy, specifically sourced images, and a well-designed web page, only for the key image to not appear.

This upcoming feature will check and notify where images have failed to render. So you can say goodbye to a white empty box ruining your page because the main banner image did not load.

We built our Analytics beta a few months ago, and we are dedicated to releasing a public version of this over the next couple of months with support for both Contensis and non Contensis users as well.

With the Contensis 17 release imminent, the Contensis team's next roadmap item is a workflow integration with Insytful. This will allow site administrators to turn on content-type-specific workflow rules to prevent editors from submitting content that does not meet certain Accessibility, SEO, or Content Quality standards.

This will be the biggest help in preventing inaccessible content from being published on your site in the future.

This feature has the ability to run searches and reports based on the content Insytful scans.

For example, you can run a policy for:

• All pages that contain a particular word.
• An HTML snippet.
• For metadata.
• All documents that have not been modified in a specific time frame.

With the addition of the analytics data, policies will be even more helpful for searches such as web pages, documents, or images that have not been visited in the past 30 days.

Duplicate page titles and meta descriptions damage SEO, accessibility and UX. If your site search returns 30 pages with the identical "Contact us | Example Company", how should anyone know which one they need?

In the future, Insytful will highlight and report if you have pages with the same title and metadata so that editors can easily review and rectify them.

Monitoring and uptime data will soon be available directly in Insytful. Site admins will be able to set up monitoring for pages and endpoints without having to go and use a different tool.

Insytful already provides a wealth of useful audits to ensure your pages are optimised for the best performance possible.

In addition, we will add checks to allow site admins to do more in-depth testing from different geolocations, with various devices and connection types. You will be able to see how users experience your content worldwide, where your assets are being served, and what could be further improved.

Although our paid plans include unlimited users, sometimes sharing a specific report with someone externally is easier. The share action allows others to view the page's results instead of inviting and adding them as users.

Soon all of these features will be added to our Roadmap to allow further feedback from users.

In this blog, we’ll highlight 10 everyday designs, principles, or features designed for accessibility but benefit everyone. There might be some features you use daily (keyboard navigation, for example) that you didn’t realise were introduced for accessibility.

That's everything we got up to in April! More features are in the pipeline. If there is anything you'd particularly like to see, make sure to add it to our open roadmap.

Impress your visitors with an accessible and usable website. Check the health of your website, spot broken links and misspellings. Know what’s working—and what’s not—on your site, free with Insytful.

Make your website work for everyone. Scan your first 100 pages for free.