This is a diagnostic report: we check whether content that only appears after JavaScript runs in a visitor’s browser is actually visible to search engines and AI crawlers, many of which have limited or delayed JavaScript rendering capability, meaning content that looks perfectly normal to a human visitor can be effectively invisible to the systems that determine your search visibility.
Server-side rendering check for JS-hidden content
A report on whether your JavaScript-dependent content is actually visible to crawlers.
- 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 the site sufficient to test rendering behaviour
- Confirmation of which pages or sections you’re most concerned about, if you have specific suspicions
- Your preferred report format, if you have one
This or something else?
| You want to know whether JavaScript-dependent content is actually visible to crawlers | This fix covers it |
| You already know content is hidden from crawlers and want it fixed, not just diagnosed | Semantic HTML remediation for extractability, the fix that follows this report |
| You want a broader machine-readability review, not specifically about JavaScript rendering | Machine-readability audit report, the broader version |
| You want your Core Web Vitals or page speed reviewed instead | A different, performance-focused report |
What we do
- Identify which content on your site depends on JavaScript to render
- Test how that content appears to crawlers with limited JavaScript execution
- Compare what’s visible to a human visitor against what a crawler with typical rendering constraints would actually see
- Flag specific instances of significant content that may be effectively hidden
- Document findings with concrete examples
- Provide a written report with recommendations, ranked by impact
What is included
- A thorough check comparing human-visible content against likely crawler-visible content
- Concrete, specific examples of any gap found
- A written, ranked report of findings
- Recommendations for addressing anything significant found
Not included
- Implementing the fixes the report recommends — quoted separately based on findings
- Guaranteeing exactly how any specific crawler renders JavaScript, since this varies and isn’t fully documented publicly
- A broader performance or Core Web Vitals assessment, a separate, related report
- Ongoing monitoring as your site’s JavaScript usage changes
Questions about this fix
How would I know if this is even a problem on my site without this report?
It's genuinely difficult to tell without deliberate testing, since the content looks completely normal to you and any human visitor — that's exactly the nature of the problem this report is designed to surface.
Do all crawlers have the same JavaScript rendering limitations?
No, capabilities vary by crawler and change over time — we test against reasonable, current assumptions about common crawler behaviour rather than a single universal standard.
Will you fix any issues found as part of this report?
Not automatically as part of the report itself — we quote separately for fixes once you know specifically what's affected, since remediation approaches vary by what's actually causing the gap.
Is this only relevant for JavaScript-heavy sites, or could a normal WordPress site be affected?
Even a fairly standard WordPress site can have this issue if certain page builder features, dynamically loaded content, or specific plugins render key content only after JavaScript executes.
How urgent is this if the report finds a real gap?
It depends on how significant the hidden content is — a decorative element rendered via JavaScript matters less than, say, key product information or main body content being effectively invisible to search and AI crawlers.
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.