Site is serving empty page shells instead of built content
If this finding appears in a report, sampled URLs returned similar initial HTML with little distinct page content. This can be intentional client-side routing or a deployment problem. The response alone does not identify the cause or establish that visitors see blank pages.
Why this matters
A real routing, asset or rendering failure can hide important content. A functioning client-rendered application needs a different assessment. Confirm the rendered experience and relevant crawler behaviour before treating the observation as a root-cause build fault.
How to fix it
Open representative deep links directly and compare initial HTML, rendered text and requested assets. Inspect status codes, console errors, host rewrites and deployment logs. If static or server-rendered content is intended but absent, check the build command and output directory against the framework and host configuration. After a supported correction, test deep links and refreshes in production and inspect the rendered content. Do not change deployment architecture solely to clear this finding.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit