In July 2025, we are migrating Sitebulb Cloud customers to new data centres, aiming to move Cloud customers to a much more stable, scalable infrastructure.
Why are we doing this?
The new infrastructure lays the foundations for Sitebulb's future; it will enable us to build and run more intensive features, and allow us to increase user limits on our plans.
Moving to a fixed set of IP addresses will also enable us to apply for 'safe bot' status for our Sitebulb Cloud user-agent with the major CDNs (e.g. Cloudflare), which should reduce crawl errors and issues in the long run.
How will this impact Sitebulb Cloud customers?
The migration should have minimal impact on your work in Sitebulb. Here are the key things to consider:
New Cloud server URL
The URL of your Sitebulb Cloud server will change - you will have received an email with the details.
Once the migration is complete, your old URL will automatically redirect to the new address. For your convenience, we recommend updating bookmarks and any other quick access links to your Cloud server with the new address.
New IP address
After the migration, your Sitebulb Cloud server will have a new IP address - you will have received an email with the details.
If you have previously whitelisted your Sitebulb Cloud server IP address in order to crawl successfully, please ensure to add your new server IP details to your server or Web Application Firewall (WAF) to avoid errors.
Minimal Downtime
Downtime during the migration should be minimal. Any audits running at the time of the migration will be temporarily suspended and resumed once the migration is completed.
In-tool Changes
This migration mainly involves changes to Sitebulb's background infrastructure, so you will not see any major changes within the UI or functionality.
However, we have made tweaks to a couple of features that you should know about:
HTML Templates will need to be renamed
We have improved the way HTML templates are classified, so you may notice slight changes to how your pages are grouped in the HTML Templates report. This should give you a more accurate page Template classification.
Once you run a new audit post-migration, your pages will be re-classified and re-grouped, and you will notice the Template names in the list revert back to default.
If you have previously customized the template names within your projects as part of your workflow, you will need to do this again.
HTML Template = Not Classified
To further improve and streamline the HTML Templates classification, Sitebulb no longer assigns templates to the following types of pages:
Non - HTML URLs
Amp pages
Paginated URLs
Orphaned & Isolated pages
URLs containing Search Parameters, Tracking Parameters, SessionId Parameters, Repetitive Parameters, Query Strings
These tend to be pages with low or no URL Rank and therefore low SEO value.
Decrease in saved External URLs/Resources
The newest Sitebulb Cloud version also includes some changes to how we process External URLs and what gets saved to your final Audit. We have refined the way Global Excluded URLs settings are followed, so more external URLs and resources may now match these settings.
You may see a small drop in the number of External URLs and external resources saved once you run a new audit after the migration. Fewer external and resource URLs collected will in turn influence the total number of Crawled URLs reported. Don't panic! All your internal URLs should still be there!
Update Desktop-Server Connection Settings
If you are connecting to Sitebulb Cloud through the desktop application, you will need to update your Connection Settings with your new Cloud workspace URL.
If you do not update your connection, you will encounter errors when trying to access Cloud audits through the Desktop application.
