Why Content Type Matters When Reviewing a Website Scan
Website intelligenceWhy Content Type Matters When Reviewing a Website Scan
A URL can return a file, image, JSON response or another content type instead of an HTML document. If you intended to scan a webpage but received a different response, the absence of normal page metadata may not mean the HTML is broken.
Check what the server actually returned
Review the content type and HTTP status associated with the request. An image URL, API endpoint or downloadable document will not contain the same title, heading and metadata structure as an HTML page.
Confirm that the URL you submitted is intended to be a public webpage. A page path copied from a developer tool may actually point to an asset or internal endpoint.
Use SiteBoost response context
The scan model records content type where available, alongside response status and final URL. Use those values to confirm that the report is describing the expected kind of resource.
If the type is unexpected, review routing and the URL before trying to correct metadata. A request that returns JSON or an image needs a different diagnostic path from an HTML document.
- Confirm the target is an HTML page.
- Check content type and HTTP status.
- Review the final URL after redirects.
- Use an appropriate tool for non-HTML resources.
Rescan the correct public page
Once you have the intended webpage address, run SiteBoost again and inspect the normal page-level findings.
Keep API endpoints and static assets separate from the public pages you include in an SEO audit.
