Long story short, a data migration led to a special character being corrupted, which resulted in this: I’m not blaming Google for this one, but the end result was a strange form of truncation that made “Google Won’t” look like “Google Won”, and made it appear that this was the end of the title. I fixed and shortened the <title> tag, and here’s what happened: Interestingly, Google opted to use the <H1> here instead of the shortened <title> version, but since it fixed the main issue, I’m going to call this a win and move on.
(2) Change isn’t easy Here’s another one where Google got it wrong, breaking the <title> tag at a parenthetical that didn’t really make any sense (similarly to the examples above): Since this was a recent and still-relevant post, we were eager to fix it. Interestingly, the first fix didn’t take. I had to resort to changing the post title (<H1>) as well, and removed the parentheses from that title. bahamas phone number database After that, Google opted for the <title> tag: This process may require some trial-and-error and patience, especially since the GSC reindexing timeline can vary quite a bit.
to kick in, but I’ve recently heard anywhere from an hour to never. (3) Don’t ditch Moz! Our final case study is a complex, multi-delimiter title where Google decided to split the title based on a phrase in quotation marks and then truncate it (without the “...”): Although the main portion of the rewrite is okay, unfortunately the cutoff makes it look like the author is telling readers to ditch Moz.
Most of these updates took about a day
-
- Posts: 441
- Joined: Sat Dec 28, 2024 3:24 am