What we look for
These pages link to localhost, 127.0.0.1 or a similar loopback address, which points at the visitor's own computer rather than at your site.
Why it matters
These links work only on the computer where the site was built, so visitors who follow one get an error instead of the page.
How to fix
Replace each local address with the live address of the page, in the CMS or page template. These links are often left behind by a site move or by content copied from a test copy of the site.
Where you’ll see it
The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.
- Terminal
- When it is one of the five findings under Fix first,
raptor crawlprints the id under it.Check: links.
localhost_ outlinks - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "links. localhost_ outlinks" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= links. localhost_ outlinks - MCP
raptor_findingswith thischeck_idreturns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.raptor_
findings { "job_ id": ". . . ", "check_ id": "links. localhost_ outlinks" }