Trust & changelog

Who runs LinkHaunter

LinkHaunter is operated by Jerome Solomons, an individual sole proprietor based in South Africa. Previously called LinkForge Digital, it is an independent product in public beta for SEO consultants, agencies, and businesses reviewing internal links.

For product questions, security reports, or data requests, contact support@linkhaunter.live. This page does not claim company incorporation, security certification, or guaranteed SEO results. Results vary.

What the product does

Add a website, verify control with a DNS TXT record, crawl accessible pages, review suggested internal links, and export them. Ownership verification expires after 30 days and must be renewed before another crawl.

Approving or exporting a suggestion does not change your website. You must implement it in your own editor. WordPress, Shopify, Webflow, and custom sites can be reviewed through their accessible web pages; native write-back and undo integrations are not available in this beta.

What we crawl and store

Crawls run only after ownership verification. The crawler checks robots.txt, follows allowed links within the submitted site, blocks private network destinations, and limits request rates. Time and plan limits can mean a crawl covers only part of a site.

We store website URLs, page titles and headings, text excerpts, internal links, crawl status, and suggestions with their review status. We also store account details, a password hash, sessions, usage, and subscription records needed to operate the service. A suggestion marked approved is not evidence that it has been implemented.

Optional AI anchor refinement sends page titles, selected headings, and short text excerpts to our AI provider, Z.ai. Do not submit sites containing confidential information you are not authorized to share. Crawl content is treated as input, not permission to change a site.

Measurement and evidence

We record new suggestions, approvals, rejections, customer implementation reports, and later crawl observations. Reporting a change is not confirmation: only a newly authorized crawl that sees the source-to-target link creates implementation evidence. It does not prove who inserted the link or which anchor text was used.

Measurement payloads use per-site pseudonymous identifiers and omit URLs, page text, titles, anchor text, and email addresses. Internal records remain linked to your account, so this is not irreversible anonymization. You can download your measurement log and its methodology from Suggestions. Earlier activity is not backfilled.

Before/after metrics cover observed internal links and word counts. Different crawl coverage cannot establish numerical improvement; these records do not measure rankings, traffic, revenue, or causal SEO impact. No customer case study is published automatically.

Retention and deletion

Site data remains in the active database while you keep the site in your account. Deleting a site removes its active page, suggestion, crawl-job, ownership-verification, and measurement-history records. This does not promise immediate deletion from backups or financial and security records.

Contact support for account deletion or other data requests. Automated account deletion and a published fixed backup-retention schedule are not available yet. Some records may need to be retained for operational or legal reasons; we will explain the applicable limits when handling your request.

Security and its limits

Account sessions and private API access are checked on the server. Passwords are stored as hashes. Crawling requires site ownership verification and includes network destination checks, robots rules, and rate limits.

These controls reduce risk; they are not a claim that the service is free of vulnerabilities or malware. No independent security certification is claimed. Please send suspected vulnerabilities privately to our support email without including passwords or API keys.

Changelog

4 November 2026

• Added DNS ownership verification before crawling, robots checks, and crawl rate and time limits.
• Made FAQ answers available in the initial page HTML with native keyboard-accessible controls.
• Published founder and data-handling information, and replaced the food-blog example with a clearly labelled insurance broker sample.
• Updated suggestion download filenames to LinkHaunter, added approved implementation worksheets and WordPress editor links, and fixed large approval batches.
• Added private lifecycle measurement logs and crawl observations. Recrawls preserve review decisions and stable page identities; unseen referenced pages are retained as cached history and excluded from current metrics.