The Fetch issue page shows a problem with fetching this page during the scan.
This is a page-level issue. It is about the page itself, not a link, image, or external target found inside the page.
What this issue means
A fetch issue means Siteimp could not load this page cleanly in the snapshot.
This can happen when:
- the page returned an HTTP error
- the request failed
- the page was blocked by
robots.txt - Siteimp could not confirm a clean final response
How to read the table
The table shows the fetch problem Siteimp recorded for this page.
Problem gives the clearest label Siteimp can provide. It may say Blocked by robots.txt, show an HTTP status, show a fetch error, or use the general label Fetch issue.
Status / error shows the status code or fetch error.
Requested URL is the URL Siteimp attempted to check.
Final URL is the final URL after redirects, when available.
Why it matters
A fetch issue can limit how much Siteimp can learn about the page.
If the page could not be fetched, Siteimp may not be able to evaluate its HTML, links, images, metadata, Lighthouse results, or page-level issues fully. Partial evidence may still be useful, but the fetch problem should be understood first.
What to check next
Open the requested URL in a browser.
If the page returns an HTTP error, fix the page, route, redirect, or server response.
If the page is blocked by robots.txt, decide whether that is intentional.
If you own the website and want deeper scanning, verify ownership and review the scan policy.
If the problem looks temporary, rerun the scan later before making a larger change.
Why this issue may be empty
If the page says No fetch issue was recorded for this page, Siteimp did not record a page-fetch problem for this page in this scan.
That does not mean every asset or link on the page is clean. It only means the page itself did not have this fetch issue.