Search Engine Optimization

  Wrong favicon in Google Search after website migration — and how we resolved it A step-by-step account of how we diagnosed, escalated, and finally resolved a brand favicon mismatch in Google Search results following a domain migration from LWReid to Trutex. The problem Following a website migration from the LWReid brand to Trutex , the correct Trutex shield favicon was showing perfectly in the browser tab — but Google Search was still displaying the old circular "LW" logo next to the site name in search results. The head of sales noticed this first: Head of Sales "The favicon is still coming up with 'LWReid' on Google Search — has this been fixed yet?" The technical lead initially suggested it was a caching issue: Technical Lead "I think it's a cached result. Is there a way to invalidate it again?" Both were partly right — but the full picture was a bit more nuanced. SEO analysis: ...

I recently handled an SEO domain migration from https://www.lwreid.com.au/ to https://www.trutex.com.au/ . The 301 server-side redirects were already live — my job was the next critical step: submitting the Change of Address in Google Search Console (GSC) . Here's exactly what happened. Challenge 1 — Wrong Access Level The client had set up GSC properties only for the non-www versions of both domains, and I was given Edit access — not Owner access. The Change of Address tool requires Owner-level access on both the old and new domain properties. I flagged this immediately, requested the correct access, and got it resolved before proceeding. Always request Owner access upfront. Edit access will block you at the submission step. Challenge 2 — Missing GSC Property for the www Destination Even though trutex.com.au had a GSC property, https://www.trutex.com.au/ did not — and these are treated as completely separate properties under the URL Prefix method. I set up the http...

Real-World Incident: How Google Indexed 9,500 Pages — Then Quietly Removed Them All A case study on AI-generated content, programmatic SEO, and the March 2026 Core Update A LinkedIn connection recently asked me to analyse their website — makdatainsights.com — a market research report platform with around 10,000 pages. What I found was one of the most textbook examples of a Google indexing trap I've seen in real time. Let me walk you through exactly what happened. The Index Graph That Tells the Whole Story Look at the Page Indexing report in Google Search Console. The pattern is striking: 7 Feb 2026 — 78 pages indexed 10 Mar 2026 — 9,528 pages indexed (peak — nearly the full 10K sitemap) 11 Mar 2026 — Drop begins. 9,292 pages. 27 Mar 2026 — March 2026 Core Update released 24 Apr 2026 — Only 2,641 pages indexed. 7,047 pages sit in "Crawled – currently not indexed" Google didn't ignore these pages. It crawled them, indexed them, reconsidered — and then s...