What to do if your website won't test
From SiteRay wiki
SiteRay can test over 97% of websites automatically, just by typing in their web address. However, some sites are more complex and require more advanced settings. Here you'll find solutions to the most common problems.
Contents |
If no/few pages are returned
We suggest you try these options one at a time, in order. Each option is not the default for a reason, so enabling all of these together in one go may have negative side effects (mostly slowing down the test):
Check the web address is correct
Visit the web address that you have entered into SiteRay, and check that it doesn't actually take you somewhere else.
e.g. visiting www.microsoft.co.uk takes you to www.microsoft.com/en/gb/
This is often overlooked by users, but prevents SiteRay from understanding where your pages really are.
If you're not sure, view your report and click Spider then Pages found. Look to see if the pages listed say "Followed redirection", and lead to a dead end. These usually mean the web address is wrong.
Change the User Agent
Edit the Settings for the website, and under the first tab (Website) change the User Agent to Internet Explorer 6 and click OK. This tells SiteRay to report itself as IE6, instead of as SiteRay - some badly behaved websites can't handle the latter and this gets around this problem.
Enable duplicate URLs
Edit the Settings for the website, and under the first tab (Website) check the Allow duplicate URLs box and click OK.
Disable index page de-duplication
Edit the Settings for the website, and under the Normalisation tab click Standard normaliser. Under De-duplication of index pages select Never exclude and click OK.
If the report crashes
There should be very few reasons why SiteRay would ever crash during a report run, but it is possible. If it does happen, please email support@silktide.com so we can prevent it from happening again.
If a report has crashed, we suggest you try the following steps one at a time, in this order:
Re-run the report
The most common cause for a crash will be we had to take the service down for essential maintenance, causing existing reports to abort. You can check our blog to see if any downtime was planned.
Test less pages
If you tried to test say 10,000 pages, try reducing this to see if this fixes the problem. Some sites try to 'lock out' anyone or thing which tries to download their content in high volume for security reasons. Testing a smaller slice of the website can circumvent this problem and others.
Disable Flash link discovery
Edit the Settings for the website, and under the Link discovery tab click Flash analyser. Uncheck the Is enabled box and click OK. This tells SiteRay not to look for links inside Flash files, which sometimes can cause instability with particularly complex sites.
If all else fails
Please contact us directly with your support enquiry. Be sure to specify what website you were testing that failed (the easiest way to do this is supply the web address you were testing).
Use the Send feedback link in the footer of SiteRay, or email support@silktide.com to get in touch.
