Experiment
● Running

Structured Data Depth

More JSON-LD schema types → richer SERP snippets → higher CTR

Experiment
● Running

AI Prompt Injection via HTML

Hidden instructions in HTML comments, aria-hidden elements, alt text, and JSON-LD fields can influence AI search summaries

Experiment
● Running

Schema Spoofing — Unearned Rich Results

Adding Product ratings and HowTo schema without matching page content still produces rich SERP results

Experiment
● Planned

Internal Link Density

Optimal internal link count per page improves crawl depth and topical authority

Not started
Experiment
● Planned

Content Freshness Signals

Updating posts with new dates (without changing content) shifts ranking

Not started
Experiment
● Planned

Hreflang Tags & Multilingual

Adding hreflang for en/sv improves English ranking due to authority signals

Not started
Experiment
● Planned

Lighthouse 95 vs 100

There is no measurable ranking difference between Lighthouse 95 and 100

Not started
Experiment
● Running

AI-Generated vs Hand-Written Content

Google cannot reliably detect or penalize AI-generated content in 2026

Experiment
● Running

AI Crawler JS Execution Detection

AI search crawlers do not execute JavaScript — only parse raw HTML. If any do, it is a VRP candidate.

Experiment
● Running

HTTP Header Canonical & X-Robots on Non-HTML

Googlebot honors Link rel=canonical and X-Robots-Tag HTTP headers on PDFs, PNGs, and JSON — edge cases (cross-origin, header-vs-meta conflict, bleed-through) may expose logic bugs.

Research Protocol

  1. Form a specific hypothesis with a measurable outcome
  2. Create isolated test pages with minimal confounding variables
  3. Document the baseline in Search Console before changing anything
  4. Wait 2–4 weeks for Google to stabilize rankings after each change
  5. Record all data: impressions, clicks, average position, CrUX data
  6. If confirmed anomaly: write up + submit to Google VRP
  7. Publish findings regardless of outcome — negative results matter