Tools
Suspicious Link Scanner
Extracts every outbound link from a page, flags anchors hidden with CSS, and groups destinations by domain so unexpected ones stand out.
Published 12 Jul 2026 · Updated 21 Aug 2026 · 3 min read
Short answer
The Suspicious Link Scanner lists every outbound link in a page's source, marks the ones that are invisible to human visitors, and groups destinations by domain so injected spam links stand out from the links you placed intentionally.
What counts as a suspicious link?
- An anchor rendered with display:none, visibility:hidden, zero font size or a large negative offset.
- A commercial destination unrelated to the page's subject.
- A domain that appears exactly once, deep in a template that renders sitewide.
- A link present only in the crawler-view response.
How do you act on the results?
STEP 01
Save the inventory
Export the list of injected URLs and the pages they appear on.
STEP 02
Clean templates, then stored content
Reinstall affected themes or plugins from source rather than hand-editing.
STEP 03
Purge caches and CDN
Cached fragments will otherwise keep serving the links.
STEP 04
Re-scan after 24 hours
Reappearance means persistence remains on the server.
Who should use this scanner?
- Owners of sites whose backlink or outbound-link profile changed without an editorial change.
- WordPress and other CMS administrators after a plugin or theme compromise, where footers and widget areas are the usual injection point.
- SEOs investigating an unexplained ranking drop where the site itself looks visually normal.
- Anyone verifying that a previous cleanup actually removed every injected anchor rather than the visible ones.
What can this scanner not determine?
- It cannot say who added a link — that requires server, CMS revision and access logs.
- It cannot see links rendered only for specific visitors unless that condition is reproduced in the request.
- It cannot classify a destination as malicious with certainty; it flags unexpected and hidden anchors so a human can judge.
- It cannot scan authenticated pages or non-public staging environments.
- It cannot remove anything: the output is an inventory used to guide a cleanup.
Common mistakes when removing injected links
| Mistake | Why it fails | Do this instead |
|---|---|---|
| Hand-editing the injected template file | Other copies of the payload remain, and the next update overwrites your fix | Reinstall the theme or plugin from source, then re-apply legitimate customisations |
| Deleting links but not the backdoor | The attacker still has write access and re-injects | Audit accounts, files and scheduled tasks before cleaning content |
| Skipping cache and CDN purge | Cached fragments keep serving the links to visitors and crawlers | Purge every layer, then re-request the page with cache-busting |
| Disavowing the links in Search Console | Disavow addresses inbound links, not outbound injections | Remove the injection at source; no disavow is needed |
Sources
- Link spam policies — Google Search Central
Prefer summary updates? Subscribe to the newsletter.