Page MenuHomePhabricator

[Regression] Google is indexing "§" characters in search result excerpts
Closed, ResolvedPublic

Description

And there is no space between § and the heading title.

https://www.google.co.uk/search?q=strunt

strunt - Wiktionary
en.wiktionary.org/wiki/strunt
§Swedish[edit]. §Noun[edit]. strunt n. nonsense; that which is not worth paying attention to. §Declension[edit]. [show ▽]Declension of strunt ...

Event Timeline

Krinkle raised the priority of this task from to Needs Triage.
Krinkle updated the task description. (Show Details)
Krinkle added a subscriber: Krinkle.
greg triaged this task as Unbreak Now! priority.Mar 17 2015, 9:26 PM

Change 197424 had a related patch set uploaded (by Krinkle):
Emergency remove .mw-headline-anchor

https://gerrit.wikimedia.org/r/197424

Change 197424 had a related patch set uploaded (by Krinkle):
Emergency remove .mw-headline-anchor

https://gerrit.wikimedia.org/r/197424

Shall we also remove the edit link while we're at it?

Shall we also remove the edit link while we're at it?

Please don't. I don't think I'm the only one who finds it immensely useful, especially on large pages.

Change 197428 had a related patch set uploaded (by Krinkle):
Emergency remove .mw-headline-anchor

https://gerrit.wikimedia.org/r/197428

Change 197424 merged by jenkins-bot:
Emergency remove .mw-headline-anchor

https://gerrit.wikimedia.org/r/197424

Change 197428 merged by jenkins-bot:
Emergency remove .mw-headline-anchor

https://gerrit.wikimedia.org/r/197428

greg assigned this task to Krinkle.

Shall we also remove the edit link while we're at it?

Please don't. I don't think I'm the only one who finds it immensely useful, especially on large pages.

I'm pretty sure @Krenair was being facetious here. :-)

I have the same question, though: why in "§Swedish[edit]" does the "§" warrant an "unbreak now!" when you can clearly see "[edit]" there as well? I guess the suspicion here is that this change broke Google's parsing? Google is screen-scraping (kind of by its nature), so it can and should expect changes to our markup. Auto-generated search results should not dictate feature development.

That said, I too would support a JavaScript or CSS implementation here, which would likely be cleaner. I guess it's back to T18691: RFC: Section header "share" link.