Take the Site Validator tour

While we're always trying to build the simplest interface for site validation, we're conscious that there's a lot of information contained in the reports.

As we don't want you to miss anything, we've built a quick step-by-step introduction to the main sections of a report.

Did you know, for example, that you can see the exact line and column where a validation issue is happening on your source code?

Screenshot of the Site Validator tour

Deep link scraping is now optional

When you submit a site URL for validation in Site Validator, our link spider visits it and enqueues it and its directly linked pages for validation.

Ideally, you should submit an XML sitemap containing the exact URLs that you want us to validate, but most developers prefer to submit just the main URL of the site, and let us discover the pages of the site by following internal links.

That's what we call deep link scraping.

Until now, we've done this automatically for you, but there are some cases where it would be convenient to disable deep link scraping.

The main case where you'd like to disable this feature is when you're submitting an XML sitemap to speficy exactly which URLs you want us to validate, so you don't want us to follow any link to add more pages. By disabling this, we'll just validate exactly what you tell us to validate.

For the rest of the cases, it's convenient to leave this option enabled; for example, you might be surprised to see that our link spider has found (and validated) pages you had forgotten long time ago, and it might help to find broken URLs in your site.

Screenshot of the Deep Link Scraping option

Sortable columns

You can now order the list of validated URLs in a sitemap by any of its columns.

This is particularly useful to order them by the number of HTML or CSS issues, like this:

sortable columns screenshot

We hope this makes it easier for you to work on fixing those errors!

Unreachable pages

We've improved the interface of site validation reports, to give more visibility to unreachable pages.

Now, those pages that respond with statuses like 404, 500, etc., will be shown in a separate tab, like this:

Unreachable pages screenshot

You can click on each page to see more details, like the exact response status code and the page that is linking to it, so you can fix the link.

We hope this saves you even more time on your web validation workflow!

Get your validation results by email

Getting your site validation results is now easier: we're now including the main issues found on your sites on the report email.

Take a look, this is an example email including the main issues found on our dummy site. Clicking on each issue takes you directly to a page with its details, so you can see the affected pages and re-check as you fix them.



Alert emails is a free feature for all our users. We hope this makes you save even more time in your web validation workflow! 

Storing versions of your site validation reports

Until now, you could only have the latest validation results for your sites stored on Site Validator. When you re-checked a site, the old results where replaced with the latest results.

We've just changed that so, from now on, you can store different versions of your site validation reports.

Comparing results

A new validation workflow that this new feature enables is storing a history of your validations.

For example, let's suppose one of your clients wants you to fix a site. You can run a site validation, and have these results as a reference. Then, you can fix all the validation errors and run more reports, and they will all be stored. Finally, you can show your clients the "before" and "after" of your work.

Different options for the same site

You also can customize the options on each site validation report, so for example, you can generate a report to validate only HTML on 500 pages, and a separate report for the same site to validate only CSS on just 5 pages.

Sharing reports with your clients and colleagues

It's now easier to share a site validation report with other people, like your clients or colleagues, even if they don't have an account on Site Validator.

To share a site report, you just need to send them its URL. You can use the sharing icons on the left sidebar to send it via email, or if you want, you can share this on social networks to show your progress. 

Pricing changes

With these latest improvements, we've changed a bit how pricing works, check out the Pricing page to see how many stored sitemaps and credits each subscription plan offers. For subscriptions created before this change, we'll still apply the same credit amount that was in effect on the time of the subscription.

UPDATE:

All users with an active subscription have unlimited storage of site reports now.

Happy validating!

Custom reports

Do you know what's cooler than being able to validate HTML and CSS on your sites with a single click?

Being able to validate just HTML, or just CSS, if you wish.

Enter custom reports

Today we've launched a new version of Site Validator that puts you in control of the kind of validations you wish to perform on your sites. You'll also be able to set the maximum number of pages you want to validate, from a minimum of 1 to a maximum of 2,000 pages.

To start a site validation you just need to enter the starting URL and set the desired options. As you change them, we'll give you an estimation of the time and cost needed to perform it. When you're happy to begin, just click "Start validation".

The interface has been simplified, now it's easier to see the progress of the validation and the results. You don't need to wait as you'll be notified by email when the validation is finished, but it's nice to watch it while it does the hard work for you anyway :D

You can also re-check individual pages, so you don't need to validate the entire site again and again if you just fixed some of the pages.

Check it out on this short video:




So, should I validate CSS for my entire site?

You may be wondering, why is CSS validation turned off by default now? The answer is that, in most cases, you don't really need to validate CSS for all the pages in your site. If you follow the web design best practices, you'll put all your CSS styles in external stylesheets and avoid using inline styles in your pages. This way you're getting a better organized site, and also helps with the performance as the stylesheets will be cached by the browser.

If you validate CSS for every page in your site it will take much longer to validate the site, as the W3C CSS validation software will need to validate your external stylesheets linked to every single page. And, you'll be notified of the same CSS errors for every page that uses these styles.

Also, when you're using third party styles like for example those in the Twitter Bootstrap framework, it can be nearly impossible to achieve 100% valid CSS.

So, our recommendation is: when site-wide validating, check the HTML syntax for every page in your site (as they're all different), but validate CSS separately (using the W3C CSS validator directly if you only have one stylesheet, or validating a sitemap linking to the different stylesheets if you have many).

How many pages should I validate?

When we launched Site Validator, you could validate up to 100 pages per sitemap. Later we increased it to 250 pages, and now we've set the limit to 2,000 pages per sitemap.

But does that mean you should validate always two thousand pages on your site?

Absolutely not.

Let's imagine you're in charge of developing the new version of a popular site like NBC.com. According to Google, this site has more than 63 million web pages. Should you try to validate 63 million pages, really? Nonsense.

What you'd do instead is prepare a sitemap with a selection of pages from the different sections, and validate only those. If you have a template for a kind of page, you only need to validate it once, not the hundreds of thousands of pages that might be using this template.

That's why you're free now to validate up to 2,000 pages per sitemap, but you can also specify a much lower limit, for example validating 25 pages might be enough in most cases. It depends on your site.

Double credits!

Now that you're able to specify how many validations you want to make, you'll be charged separately for HTML and CSS validations. For example, if you validate just HTML you'll spend one credit per each validated page; if you validate HTML and CSS, you'll spend two credits per each validated page.

We're also doubling the number of credits you get with your subscription, for example the Freelancer subscription that had 5,000 credits per month, now has been increased to 10,000 credits per month. So you'll be able to keep validating HTML and CSS on your sites for the same price, or validate the double amount of pages if you only validate HTML.

We hope these improvements help you create amazing, more valid, web sites! Let us know how it goes for you.

If you haven't yet tried Site Validator, what are you waiting for? Remember there's a 30-days money back guarantee for all our subscription plans!

Start validating your sites now.

UPDATE September 3rd: we've increased the maximum number of pages per sitemap to 2,000 pages. Happy validating!

Yearly subscriptions

Site Validator is a subscription-based service. You choose a plan, and you get a number of credits that you can use to validate your web sites.

Until now, we've been offering monthly subscriptions, so you get your initial load of credits when you subscribe and they're recharged, and you're invoiced for, every month.

Beginning today, we're also offering yearly subscriptions. By choosing one of the annual plans, you get all the credits for the 12 months at once, and they're recharged yearly.

This also means that you'll only get one invoice per year from us, less paperwork, yay!

And last but not least, you'll also get an important discount, you get 12 months for the price of 10.

For example, if you subscribe to the Freelancer plan, yearly, you'll get 60,000 credits to validate your pages for only $240/year (instead of the $24x12 = $288 that you'd pay per year with the monthly subscription).

Check out the new yearly subscription plans:

https://app.sitevalidator.com/pricing?payment=yearly

Fifteen Servers: a look at our internal architecture

At Site Validator we strive to provide the simplest way to validate the markup of your sites, so all you need to do is enter an URL and click a button, but if like us you're passionate about tech stories, here's a description of our current setup, which involves the collaboration of (at least) fifteen servers to get the job done:

Fifteen Servers

Introducing the Site Validator Forum

We're happy to announce the launch of the Site Validator Forum, and welcome all web developers to talk about web validation. Need help about fixing a particular error, want to help others, or want to share a brand new tool or technique you've just discovered? Do so at the new forum.



The forum is open to everyone to participate, you don't need a Site Validator account to log in (you can log in using your Twitter, Facebook, Google, Yahoo or Github account). Initially we've set up categories for HTML, CSS, JavaScript and Accessibility, but feel free to suggest others.

We've chosen the state-of-the-art Discourse platform for the new forum. Discourse is great for building online communities, very simple to use, and is specially good for talking about code thanks to its built-in syntax highlighting.

See you at the forum!




<< previous page

Page 2 of 6

next page >>