Revenge SEO: How a fired contractor erased 90% of our traffic
Pro Revenge SEO: How a fired contractor erased 90% of our traffic Opinion By Scott Mazza Published 30 July 2026 Revoking access is a security event, not an afterthought When you purchase through links on our site, we may earn an affiliate commission. Worse, the content was AI-written and keyword-stuffed. Scott Mazza Social Links Navigation Co-Founder of Vitality CBD.
- ▪Pro Revenge SEO: How a fired contractor erased 90% of our traffic Opinion By Scott Mazza Published 30 July 2026 Revoking access is a security event, not an afterthought When you purchase through links on our site, we may earn an affiliate c
- ▪Worse, the content was AI-written and keyword-stuffed.
- ▪Scott Mazza Social Links Navigation Co-Founder of Vitality CBD.
TechRadar publishes from United Kingdom and files mainly under tech. We currently carry 1,363 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | TechRadar |
| Canonical URL | https://www.techradar.com/pro/revenge-seo-how-a-fired-contractor-erased-90-percent-of-our-traffic |
| Publication time | Thu, 30 Jul 2026 09:49:31 +0000 |
| Retrieval time | 2026-07-30T09:52:00.045Z |
| Last seen | 2026-07-30T09:52:00.045Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 0Rj0UPT-AhZ7 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Pro Revenge SEO: How a fired contractor erased 90% of our traffic Opinion By Scott Mazza Published 30 July 2026 Revoking access is a security event, not an afterthought When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works. (Image credit: Shutterstock) Copy link Facebook X Whatsapp Reddit Pinterest Flipboard Threads Email Share this article 0 Join the conversation Follow us Add us as a preferred source on Google Newsletter Subscribe to our newsletter Last year, I brought on a new specialist in search engine optimization (SEO) to drive backlinks and business, only to find the contractor used black-hat practices to generate toxic, irrelevant results. Worse, the content was AI-written and keyword-stuffed.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at TechRadar.