Detect and resolve malicious canonical tags or redirects.
- Detect and resolve malicious canonical tags or redirects1 cited source1 category
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Malicious code injecting cross-domain canonicals or redirects can hijack SEO value and harm site trust.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- Conduct security scans for injected HTML or HTTP headers.
- Inspect page source for canonical tags pointing to unexpected external domains.
- Audit server and CMS files for compromised code or scripts.
- Clean and restore affected files; update passwords and access control.
- Verify removal by testing pages in Google URL Inspection tool.
Watch for
Spam or hacked canonical tags redirect SEO value to spammy external sites.
Definition of done
No malicious canonical or redirect code exists in source or HTTP headers verified by security scans.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.