Finding internal links to a preview deployment
Find preview-deployment links by searching internal destinations for nonproduction hosts, then verify every match in context. A preview URL in an article example and a navigation link to staging require different decisions.
Define the host boundary
Create a short list of approved public hosts and known preview hosts. Include alternate domains only when their purpose is understood. This list is an audit aid, not a search-engine rule. Keep the intended production destination beside each preview host when that relationship is known.
Inspect matched references
Record source URL, visible anchor, href, placement and destination purpose. Check navigation, article bodies and shared components. Determine whether the reference is an illustrative example, a deliberate external resource or an accidental route away from the public site. Do not replace plain text blindly just because it resembles a preview address.
Choose the equivalent destination
For an accidental link, confirm the public page exists and serves the same purpose before changing the href. Avoid mapping every preview page to the homepage. When multiple public variants represent duplicate content, align the reference with the intended preferred URL without claiming that a canonical signal guarantees selection.
Check the published result
Follow the edited link from its real source page and inspect other instances supplied by the same component. Record the old host, new destination, reason and verification date. A clean search in source files is useful but should be paired with displayed-link readback. Begin a wider investigation at /website-analyzer/ if the host mismatch affects more than this path.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Is a preview hostname always an error?
No. Context matters. A deliberate documentation reference is different from a service link accidentally sending readers to an unfinished deployment.
Can I replace the host automatically?
Only after checking path equivalence. A matching path string does not establish that the public destination contains the intended information.