We run your key templates through the official W3C HTML and CSS validators and hand you a findings list — catching structural markup errors that browsers often silently correct or ignore, but which can cause inconsistent rendering or accessibility issues you might not otherwise trace back to invalid code.
W3C HTML & CSS validation sweep
Every template validated against the official W3C HTML and CSS standards.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Access to browse the templates you want validated
- Confirmation of which page types matter most, if any
- Whether you want straightforward fixes made directly, or the list handed to you first
This or something else?
| You want your templates checked against the official W3C HTML and CSS validators | This fix covers it |
| You want accessibility specifically checked, not general markup validity | WAVE accessibility scan & findings report, or axe DevTools audit |
| You want schema/structured data validity checked instead of general markup | Schema.org validator sweep across templates |
| JSON-LD schema is broken specifically by your page builder | JSON-LD broken by page builder – repair |
What we do
- Identify every distinct template in use across the site
- Run each through the official W3C HTML and CSS validators
- Record every structural error found, distinct from stylistic preferences
- Prioritise the list by how many pages each issue affects
- Fix straightforward, low-risk issues directly where the cause is clear
What is included
- A validation sweep across every distinct template
- A prioritised list of structural markup errors
- Straightforward issues fixed directly
- A quote for anything requiring larger work
Not included
- Accessibility-specific issues beyond general markup validity — a separate, related check
- Schema or structured data validity — a separate, related check
- A visual redesign of any template, beyond correcting invalid markup
- Ongoing monitoring for future validation errors
Questions about this fix
Does invalid HTML actually matter if the page looks fine?
Often, yes, even when nothing looks visibly wrong — browsers are forgiving and silently correct many errors, but that correction can behave inconsistently across browsers, and invalid markup can also confuse assistive technology.
Is this the same as an accessibility audit?
No — general markup validity and accessibility compliance are related but distinct, since a page can be perfectly valid HTML and still be inaccessible, or occasionally the reverse.
Will every page on my site get checked?
We check every distinct template, since pages sharing a template typically share the same underlying markup errors.
What kind of issues does this typically catch?
Unclosed tags, improperly nested elements, invalid attribute values, and deprecated markup are common examples, often introduced by page builders or old, uncleaned code.
Does invalid markup carry any real SEO penalty on its own?
Not directly in most cases — search engines are generally forgiving of minor markup errors, though cleaner code does support related technical factors like accessibility and consistent rendering.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.