Opened 10 years ago

Closed 8 years ago

#507 closed defect (bug) (worksforme)

Exclude Footer from Google search results

Reported by: siobhan's profile siobhan Owned by: otto42's profile Otto42
Milestone: Priority: normal
Component: General Keywords:


I do a lot of Google site searches on, for example, I might use the following search string on Google "site: Kubrick" to find out information about the Kubrick theme. Sometimes I'll drill down further to search just the news blog or the support forums.

I encounter a problem, however, when I search for any keywords which are contained within the footer. The search string "site: bbpress" brings up all of the pages with the word bbpress, which is every page:

In order to make search results more relevant, I suggest following Google's advice for excluding boilerplate content:

From Google:

If your pages have regions containing boilerplate content that's not relevant to the main content of the page, you can identify it using the nocontent class attribute. When Google Custom Search sees this tag, we'll ignore any keywords it contains and won't take them into account when calculating ranking for your Custom Search engine. (We'll still follow and crawl any links contained in the text marked nocontent.) To use the nocontent class attribute, you'll need to tag the boilerplate content, and then modify your context file. This tells Google that you're using the nocontent class attribute.

Change History (6)

This ticket was mentioned in IRC in #wordpress-meta by sams. View the logs.

10 years ago

#2 @Otto42
10 years ago

  • Owner set to Otto42
  • Status changed from new to assigned

#3 @joostdevalk
9 years ago

This won't fix it for Google searches, only for a custom site search engine...

#4 @SergeyBiryukov
9 years ago

  • Keywords needs-patch removed

Removing 'needs-patch' from components that are not open sourced yet, to help focus on tickets that actually need a patch.

This ticket was mentioned in Slack in #meta by ocean90. View the logs.

8 years ago

#6 @ocean90
8 years ago

  • Resolution set to worksforme
  • Status changed from assigned to closed

Looks like this isn't an issue anymore, closing as worksforme.

Note: See TracTickets for help on using tickets.